{"version":"2.1.267","anchor":"non-blocking-stdout-can-now-be-enabled-by-a-remote-flag-not","canonical_anchor":"non-blocking-stdout-can-now-be-enabled-by-a-remote-flag-not","heading":"Non-blocking stdout can now be enabled by a remote flag, not just an env var","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/non-blocking-stdout-can-now-be-enabled-by-a-remote-flag-not","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Non-blocking stdout can now be enabled by a remote flag, not just an env var\n\nNon-blocking stdout writes can now be turned on remotely, not just via an environment variable\n\n**What**\n\n`CLAUDE_CODE_NONBLOCKING_STDOUT` makes Claude Code write terminal output through a second, non-blocking channel so a stalled terminal (like a paused tmux pane or a frozen SSH connection) can't freeze the session. Previously this only applied when the environment variable was explicitly set. Now, if the environment variable isn't set, Claude Code also checks a remote server-controlled setting, `tengu_event_loop_stall`, as well as an internal first-party check, to decide whether to enable it.\n\n**Why**\n\nThis lets Anthropic roll out the non-blocking stdout behavior to more users gradually via a remote setting, without requiring everyone to manually set the environment variable themselves.\n\n- Flag `tengu_event_loop_stall`: Off in both readings (read for one account on one subscription tier against v2.1.267; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Terminal UI\n- Names: `CLAUDE_CODE_NONBLOCKING_STDOUT`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}