{"version":"2.1.292","anchor":"wakeup-scheduling-restored-on-resume-and-hooks-worker-respaw","canonical_anchor":"wakeup-scheduling-restored-on-resume-and-hooks-worker-respaw","heading":"Scheduled wakeups survive a resume, and a crashed hooks worker is restarted","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/wakeup-scheduling-restored-on-resume-and-hooks-worker-respaw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Scheduled wakeups survive a resume, and a crashed hooks worker is restarted\n\nResuming a session restores a pending scheduled wakeup, and if the background process that runs hooks dies, Claude Code restarts it and retries once\n\n**What**\n\nThis release brings three changes:\n\n- Scheduled wakeups: when you resume a session (pick up an earlier conversation where it left off), Claude Code looks back through it and restores any scheduled wakeup that was still pending.\n\n- The hooks worker: hooks are commands or scripts you configure to run at set points while Claude Code works. If the background process that runs them dies, Claude Code now starts a new one and tries again once.\n\n- Plugin reloads: when that hooks process reloads its code, it now takes the whole set of plugins into account.\n\n**Why**\n\nA wakeup you scheduled is less likely to be lost when you resume, and one crash of the hooks process no longer has to stop your hooks from running.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}