Files
paseo/packages
2eba291a8e Keep idle Claude agents running while a session cron or /loop wakeup is pending (#9744)
* fix(claude): keep an idle agent running while it has a session cron

Claude keeps session-only crons and /loop wakeups in its own process, so
stopping that process drops them. The idle runtime cleanup asked the Claude
session whether it could stop, and the session never knew about these jobs:
they appear nowhere on the message stream.

Claude lists them as session_crons on every Stop hook. The session now
records that list, and canStopRuntime() refuses while it is non-empty. The
next Stop after a fire, a CronDelete or an expiry updates the list.

Co-authored-by: KronixDev <35991992+KronixDev@users.noreply.github.com>

* refactor(claude): type the Stop hook with the SDK's hook input

Co-authored-by: KronixDev <35991992+KronixDev@users.noreply.github.com>

* fix(claude): hold the runtime after a cron tool call until the next Stop

Claude lists session crons only in the Stop hook, and runs Stop only for
turns that complete. A turn that called CronCreate and was interrupted or
failed left the count at zero, so idle cleanup could still stop the
process holding the cron. A CronCreate, CronDelete or ScheduleWakeup call
now marks the count unknown until the next Stop reports it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>
Co-authored-by: KronixDev <35991992+KronixDev@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 10:01:41 +00:00
..