You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
LoopArea: what it touches
Bug FixesKind: in v2.1.292,
Bug FixesSection of the release
Unclear It is not known whether the scheduler that does this is switched on for a given account.
What
Claude 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.
Now the scheduler behaves differently once input has closed:
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.
A count of pending wakeups keeps the session parked and waiting rather than exiting.
Tasks claimed through a lease file are still not taken.
Why
Runs 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not known whether the scheduler that does this is switched on for a given account.
Anthropic's release notes agreeFixed a background session's /loop silently stopping when the session's process restarted (for example after a crash), because its pending…
