{"version":"2.1.251","anchor":"two-dispatch-implementations-selected-by-the-same-switches","canonical_anchor":"second-api-routing-path-off-unless-you-turn-it-on","heading":"New dispatch-v2 routing gate for outbound API requests","tier":"use","area":"API Routing","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/two-dispatch-implementations-selected-by-the-same-switches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### New dispatch-v2 routing gate for outbound API requests\n\nTwo alternate internal dispatch implementations are selectable by environment variables, both off by default.\n\nA new function selects the outbound API dispatch route based on environment variables `CLAUDE_CODE_DISPATCH_V2D` and `CLAUDE_CODE_DISPATCH_V2S`, falling back to remote flags `tengu_dreamy_frost` and `tengu_cedar_lattice` respectively when the env vars are unset. Both gates default off.\n\nIf `CLAUDE_CODE_DISPATCH_V2D` (or `tengu_dreamy_frost`) is set, outbound requests get the `anthropic-dispatch-id: v2d` header; else if `CLAUDE_CODE_DISPATCH_V2S` (or `tengu_cedar_lattice`) is set, they get `v2s`; otherwise no header is sent and the old routing path is used. A companion telemetry event, `cli_api_route_observed`, fires once per process to record which route was actually used.\n\n- Flag `tengu_dreamy_frost`: Not enough to say (read for one account on one subscription tier against v2.1.251; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Flag `tengu_cedar_lattice`: Not enough to say (read for one account on one subscription tier against v2.1.251; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: API Routing\n- Names: `CLAUDE_CODE_DISPATCH_V2D`, `CLAUDE_CODE_DISPATCH_V2S`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}