{"version":"2.1.232","anchor":"forked-subagents-are-on-by-default","canonical_anchor":"forked-subagents-are-on-by-default","heading":"Forked subagents are on by default","tier":"use","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/forked-subagents-are-on-by-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Forked subagents are on by default\n\nForked subagents are on by default in interactive sessions; set `CLAUDE_CODE_FORK_SUBAGENT` to false to opt out.\n\n**What**\n\nSubagent 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.\n\n**Details**\n\n- The previous remote-config flag `tengu_copper_fox` is gone; the resolver returns the literal `\"default\"` unless one of the three conditions above applies.\n- The telemetry event `tengu_fork_subagent_enabled` now reports source `default` rather than `gb_rollout` or `disabled`.\n- The resolved source is cached in per-session state rather than a module-level variable, so it is decided once per session.\n\n**Evidence**\n\n`tengu_fork_subagent_enabled`\n\n- Flag `tengu_copper_fox`: Off in both readings (read for one account on one subscription tier against v2.1.232; this account: off, anonymous baseline: off, compiled default: 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.\n- Area: Subagents\n- Names: `CLAUDE_CODE_FORK_SUBAGENT`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}