{"version":"2.1.299","anchor":"stderr-writes-are-bounded-dropped-messages-reported","canonical_anchor":"stderr-writes-are-bounded-dropped-messages-reported","heading":"Claude Code drops stuck error output instead of waiting on it","tier":"notice","area":"Performance","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/stderr-writes-are-bounded-dropped-messages-reported","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Claude Code drops stuck error output instead of waiting on it\n\nIf error output backs up for over 10 seconds and 1 MiB, Claude Code now drops it and leaves a notice saying messages were dropped\n\n**What**\n\nStandard error, or stderr, is the channel programs use for error and status messages. If messages written there back up for more than 10 seconds and more than 1 MiB, Claude Code now drops them and writes a notice in their place saying messages were dropped. The debug log gets a similar note.\n\nFor background sessions, advice about command-line flags now says to run `\/stop`, then `claude --resume` from your shell.\n\n**Why**\n\nA program that stops reading Claude Code's error output can no longer make Claude Code hang. Some of those messages may be lost, and the notice tells you so.\n\n- Area: Performance\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}