{"version":"2.1.235","anchor":"new-per-conversation-atis-latch-persisted-and-resumed-wit","canonical_anchor":"new-per-conversation-atis-latch-persisted-and-resumed-wit","heading":"New per-conversation \"ATIS\" latch, persisted and resumed with the session","tier":"soon","area":"ATIS Latch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/new-per-conversation-atis-latch-persisted-and-resumed-wit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### New per-conversation \"ATIS\" latch, persisted and resumed with the session\n\nNew per-conversation \"ATIS\" latch persists across fork\/resume, taking priority over live config once set\n\n**Unclear.** Nothing has been read about the `tengu_kestrel_moor` gate, so whether or how this feature is enabled is unknown.\n\nA new latch, alongside the existing sticky betas and per-turn effort pins, is now stored on the conversation. It is written into the session state file as `{ type: \"atis-latch\", sessionId, atis }`, merged with \"always\"\/\"last-wins\" semantics like the existing isolation-latch, and carried through fork and resume via `atisLatchAtEntry` and the session-state snapshot APIs. Its value originates from client config (`atis`), and once latched it is preferred over the live config for the rest of the conversation.\n\n- Flag `tengu_kestrel_moor`: Not enough to say (read for one account on one subscription tier against v2.1.235; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: ATIS Latch\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}