{"version":"2.1.242","anchor":"gateway-routing-is-passed-down-to-spawned-agent-team-process","canonical_anchor":"gateway-routing-is-passed-down-to-spawned-agent-team-process","heading":"Gateway routing is passed down to spawned agent-team processes","tier":"use","area":"Agent Teams","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/gateway-routing-is-passed-down-to-spawned-agent-team-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Gateway routing is passed down to spawned agent-team processes\n\nCLAUDE_CODE_USE_GATEWAY now passes down to spawned agent processes, so gateway routing is no longer dropped.\n\n**What**\n\n`CLAUDE_CODE_USE_GATEWAY` is now on the allowlist of environment variables copied into processes Claude Code spawns, alongside the other provider switches such as `CLAUDE_CODE_USE_BEDROCK` and `CLAUDE_CODE_USE_MANTLE`, so a session routed through an enterprise gateway hands that routing down instead of dropping it.\n\n**Details**\n\n- Unconditional for anyone who has the variable set.\n\n**Evidence**\n\n`CLAUDE_CODE_USE_GATEWAY`\n\n- Area: Agent Teams\n- Names: `CLAUDE_CODE_USE_GATEWAY`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}