Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ATIS LatchArea: what it touches
In DevelopmentKind: in v2.1.235,
What probably matters to youSection of the release
Unclear Nothing has been read yet about the tengu_kestrel_moor gate, so whether this latch behavior is active for any account is unknown.
A new gate makes the client's atis value get read once per conversation into a latch, seeded only when the value is printable ASCII, instead of re-reading client data on every access. When the gate is off, the old behavior of reading it directly each time is kept.
Read from
Feature flag
tengu_kestrel_moorNot 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.235: on
Flag reading movedThe flag server now returns off for tengu_kestrel_moor, 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.
Flag reading movedThe flag server now returns nothing at all, having stopped carrying it for tengu_kestrel_moor, 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtNothing has been read yet about the `tengu_kestrel_moor` gate, so whether this latch behavior is active for any account is unknown.
The name it cites is new in this buildNew in this build: tengu_kestrel_moor
