Checkpoints now record self-scheduling wake counts and open artifact watches, though the loop itself is off.
Loop state survives handoff, but the loop is behind tengu_kairos_loop_dynamic, which falls back to false.
tengu_kairos_loop_dynamic On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.234: on
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
What's wrong with this entry?
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.