{"version":"2.1.295","anchor":"resume-restores-a-pending-loop-wakeup-or-reports-it-as-mis","canonical_anchor":"resume-restores-a-pending-loop-wakeup-or-reports-it-as-mis","heading":"Resumed sessions restore a pending \/loop wakeup or say it was missed","tier":"notice","area":"Loop","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/resume-restores-a-pending-loop-wakeup-or-reports-it-as-mis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Resumed sessions restore a pending \/loop wakeup or say it was missed\n\nOn resume, a `\/loop` wakeup still in the future is set again, and one whose time has passed is reported as missed\n\n**What**\n\n`\/loop` runs a prompt again and again, and Claude can use the ScheduleWakeup tool to set when the next run happens. When you resume a session, Claude Code now looks at the last wakeup it set:\n\n- If its time is still in the future, the wakeup is set again and will fire.\n\n- If its time has already passed, Claude is told the wakeup will not fire and to ask you before scheduling it again. The loop stays stopped until Claude schedules it again, and you can reply to continue it.\n\n**Why**\n\nA loop no longer quietly stops when a session is restarted; it either carries on or you are asked whether to continue.\n\n- Area: Loop\n- Names: `\/loop`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}