Unclear The condition under which CLAUDE_CODE_MAIN_REPLY_HOLD_MS takes effect is not stated.
Claude Code can already hold back streamed replies that nobody is watching. It now has a setting for the main conversation too, plus two more. Each is an environment variable, a named value you set before starting Claude Code:
CLAUDE_CODE_MAIN_REPLY_HOLD_MSsets how long, in milliseconds, replies in the main conversation are held before being passed on. It defaults to 0 and only takes effect under a certain condition.CLAUDE_CODE_STREAM_TIMER_SLACK_MSgives slack, in milliseconds, to the timer that gives up on a reply when no data arrives for a while, so the timer is not reset on every small piece. When it is not set, the value comes from a remote setting that falls back to 0. It is kept between 0 and a maximum.CLAUDE_CODE_MCP_SERVE_TUNNEL_BINARY_FRAMESasks for binary frames, a compact data format, on a tunnel used when Claude Code serves MCP. It is cleared for programs Claude Code starts.
The timer slack cuts down on how often the stream timer is reset during a reply. With nothing set, all of these stay at their defaults of no slack and no holding.
tengu_fuzzy_spindle Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.318: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.318. It isn't a statement about your account. What a flag value here can and cannot tell you
The condition under which `CLAUDE_CODE_MAIN_REPLY_HOLD_MS` takes effect is not stated.
New in this build: tengu_fuzzy_spindle