Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.267 ·

Non-blocking stdout can now be enabled by a remote flag, not just an env var

Non-blocking stdout writes can now be turned on remotely, not just via an environment variable

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaTerminal UIwhat it touches
KindImprovementsin v2.1.267,
You'll notice

Non-blocking stdout writes can now be turned on remotely, not just via an environment variable

What

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.

Why

This 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.

Read from
Names in the bundleCLAUDE_CODE_NONBLOCKING_STDOUT
Feature flag
tengu_event_loop_stall Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.267: off

Read once, for one account on one subscription tier, against v2.1.267. It isn't a statement about your account. What a flag value here can and cannot tell you

What the documentation says
What has happened since
Flag reading moved The flag server now returns on for tengu_event_loop_stall, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Gate removed from the code v2.1.227 removed the tengu_event_loop_stall gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_event_loop_stall

See this entry in the whole of v2.1.267 →