The pinned atis value is set once per conversation and only accepts printable ASCII.
tengu_kestrel_moor 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.235: off
Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The latch that pins the client atis value is seeded a single time per conversation and only accepts a value that is printable ASCII, which keeps stray bytes out of it.
- Gated on
tengu_kestrel_moor, a remote flag whose fallback is on; with the gate off, each read goes straight to client data as before.
tengu_kestrel_moor
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.228
Bundled API client: new endpoints and a stripped request field
Both mention client
-
v2.1.228
Bundled Anthropic SDK picks up beta resources
Both mention client
-
v2.1.228
API client request handling moved to a middleware chain
Both mention client