Two alternate internal dispatch implementations are selectable by environment variables, both off by default.
Second dispatch paths sit behind env vars and remote flags that 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?
Alongside the request header, the code picks between two internal dispatch implementations using the same controls: CLAUDE_CODE_DISPATCH_V2D and CLAUDE_CODE_DISPATCH_V2S, falling back to the remote flags tengu_dreamy_frost and tengu_cedar_lattice, both defaulting to off.
- With nothing set, the existing implementation runs.
CLAUDE_CODE_DISPATCH_V2D
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