Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.251 ·

New dispatch-v2 routing gate for outbound API requests

You can send API requests down a newer routing path by setting one of two environment variables.

Group of 2 Use it now Notable Nothing to try yet No documentation found In Development
JSON All of v2.1.251
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
API RoutingArea: what it touches
In DevelopmentKind: in v2.1.251,
What probably matters to youSection of the release

Two alternate routing headers are selectable by env vars; without them nothing changes and both remote flags default off.

A 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.

If 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.

Read from
Feature flag
tengu_dreamy_frost Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.251: off

tengu_cedar_lattice Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.251: off

Read once, for one account on one subscription tier, against v2.1.251. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_dreamy_frost, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_dreamy_frost

See this entry in the whole of v2.1.251 →

Feedback