Pattern: Long-Running Agent State Is Being Given a Single Canonical Home

GitHub·medium signalXBlueskyLinkedInCopy link

Cline moved agent-created schedules out of per-chat folders into `~/.cline/schedules` and fixed cron reconciliation wiping them on restart; Claude Code made background sessions hold their git worktree lock so cleanup cannot delete the checkout, and stopped resurrecting weeks-old background sessions after a reboot. Both are the same realization arriving at the same time: once agents run unattended across restarts, state scattered by whichever session created it becomes unrecoverable. If you are building an agent harness, put durable state in one user-level directory before the schedule count grows.