{"version":"2.1.292","anchor":"cronloop-tasks-can-fire-after-input-closes-while-waiting-fo","canonical_anchor":"cronloop-tasks-can-fire-after-input-closes-while-waiting-fo","heading":"Loop tasks can still fire after input closes while waiting on agents","tier":"notice","area":"Loop","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/cronloop-tasks-can-fire-after-input-closes-while-waiting-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Loop tasks can still fire after input closes while waiting on agents\n\nScheduled loop wakeups can now fire after input has closed if the run is still waiting for agents, so the session stays open instead of exiting\n\n**Unclear.** It is not known whether the scheduler that does this is switched on for a given account.\n\n**What**\n\nClaude Code has a scheduler that can wake a session up later to run a repeating \"loop\" task. Before, it skipped every scheduled run once standard input closed. Standard input is the stream a program reads its typed or piped input from.\n\nNow the scheduler behaves differently once input has closed:\n\n- Loop tasks still fire if the run is waiting for agents to finish. Agents are helper processes Claude Code starts to work on part of a job.\n\n- A count of pending wakeups keeps the session parked and waiting rather than exiting.\n\n- Tasks claimed through a lease file are still not taken.\n\n**Why**\n\nRuns with no one at the keyboard that rely on `\/loop`-style wakeups no longer stop early just because the program that started them closed its input.\n\n- Area: Loop\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}