Forked subagents are on by default in interactive sessions; set CLAUDE_CODE_FORK_SUBAGENT to false to opt out.
tengu_copper_fox Off in both readingsThe 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.232: 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.232. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Subagent forking no longer waits on a staged rollout flag. Ordinary interactive sessions now get it, and the only way to turn it off is setting the environment variable CLAUDE_CODE_FORK_SUBAGENT to false. It stays off in non-interactive sessions and when coordinator mode is active.
- The previous remote-config flag
tengu_copper_foxis gone; the resolver returns the literal"default"unless one of the three conditions above applies. - The telemetry event
tengu_fork_subagent_enablednow reports sourcedefaultrather thangb_rolloutordisabled. - The resolved source is cached in per-session state rather than a module-level variable, so it is decided once per session.
tengu_fork_subagent_enabled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Another forged control tag is escaped in subagent output
Both mention subagent
-
v2.1.234
Spawned processes get
--flag=valuewhen the value looks like a flagBoth mention subagent
-
v2.1.235
New error for delegating to a subagent without naming one
Both mention subagent