{"version":"2.1.257","anchor":"stream-json-stdin-input-now-enforces-a-line-length-budget","canonical_anchor":"stream-json-stdin-input-now-enforces-a-line-length-budget","heading":"Stream-json stdin input now enforces a line-length budget","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/stream-json-stdin-input-now-enforces-a-line-length-budget","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Stream-json stdin input now enforces a line-length budget\n\nA single stream-json stdin message now has a character budget and errors explicitly instead of buffering forever.\n\nThe CLI's stream-json stdin reader now enforces a maximum character budget for a single newline-terminated message. Exceeding it now surfaces an explicit error instead of buffering indefinitely, pointing to either a non-newline-terminated producer or a message that exceeded the budget.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}