Loop state survives handoff, but the loop is behind tengu_kairos_loop_dynamic, which falls back to false.
Session checkpoints now record how many times a self-scheduling loop has woken and what live Artifact watches were open, and each scheduled wake-up records when it is due, why, and whether it holds a keepalive budget. The loop feature itself is behind tengu_kairos_loop_dynamic, whose in-source fallback is false, so it is off absent a server value.
- The wake count is stored as a non-negative integer, so a loop's wake budget carries over instead of resetting when the session is handed off to the background.
loopWakeFires
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_kairos_loop_dynamic Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.234: off
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.