{"version":"2.1.232","anchor":"fork-subagent-setting-is-resolved-once-per-session-with-the-","canonical_anchor":"fork-subagent-setting-is-resolved-once-per-session-with-the-","heading":"Fork-subagent setting is resolved once per session, with the environment checked first","tier":"use","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/fork-subagent-setting-is-resolved-once-per-session-with-the-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Fork-subagent setting is resolved once per session, with the environment checked first\n\nSetting CLAUDE_CODE_FORK_SUBAGENT decides fork subagents up front, and the answer is cached per session.\n\n**What**\n\nThe check for whether fork subagents are enabled now evaluates the hard disable and `CLAUDE_CODE_FORK_SUBAGENT=false` before anything else, and caches the result on the session config instead of a module-level variable. Setting the variable to true reports the source as the environment; otherwise a rollout check decides.\n\n**Details**\n\n- The telemetry event for how the setting was resolved fires once, and only when the result is not disabled.\n\n**Evidence**\n\n`CLAUDE_CODE_FORK_SUBAGENT`\n\n- Area: Subagents\n- Names: `CLAUDE_CODE_FORK_SUBAGENT`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}