{"version":"2.1.295","anchor":"an-ipc-schema-is-tightened-to-a-bounded-nullable-list","canonical_anchor":"an-ipc-schema-is-tightened-to-a-bounded-nullable-list","heading":"An internal response format now carries a bounded list instead of an error reason","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/an-ipc-schema-is-tightened-to-a-bounded-nullable-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### An internal response format now carries a bounded list instead of an error reason\n\nOne internal response format changed from an error with an optional reason to an optional list of up to 1,000 text entries\n\n**What**\n\nOne of the response formats Claude Code reads internally has changed. It used to hold an error with an optional reason. It now holds an optional list of up to 1,000 text entries, each up to 64,000 characters long. If the response cannot be read, Claude Code treats it as empty instead.\n\n**Why**\n\nThe data passed through this channel now has a different shape and a fixed size limit.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}