You can send API requests down a newer routing path by setting one of two environment variables.
Two alternate routing headers are selectable by env vars; without them nothing changes and both remote flags default off.
tengu_dreamy_frost Not enough to sayNothing 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: on
tengu_cedar_lattice Not enough to sayNothing 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: on
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's wrong with this entry?
Outbound API requests can carry an anthropic-dispatch-id header selecting a newer routing path. Setting CLAUDE_CODE_DISPATCH_V2D (or the remote flag tengu_dreamy_frost) sends v2d; CLAUDE_CODE_DISPATCH_V2S (or tengu_cedar_lattice) sends v2s. With neither set no header goes out and the existing route is used. Both remote flags default off.
- The header is attached to real outbound requests, not just computed.
- A
cli_api_route_observedtelemetry event fires once per process recording which route was actually taken.
anthropic-dispatch-id
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Refusal-fallback metadata attached to requests
Both mention routing