{"version":"2.1.234","anchor":"self-scheduling-loop-state-survives-a-background-handoff","canonical_anchor":"self-scheduling-loop-state-survives-a-background-handoff","heading":"Self-scheduling loop state survives a background handoff","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/self-scheduling-loop-state-survives-a-background-handoff","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Self-scheduling loop state survives a background handoff\n\nCheckpoints now record self-scheduling wake counts and open artifact watches, though the loop itself is off.\n\n**What**\n\nSession 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.\n\n**Details**\n\n- 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.\n\n**Evidence**\n\n`loopWakeFires`\n\n- Flag `tengu_kairos_loop_dynamic`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.234; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Sessions\n- Names: `tengu_kairos_loop_dynamic`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}