[DOCS] Scheduled tasks docs omit `--resume`/`--continue` restoration

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/scheduled-tasks

Section/Topic

Run prompts on a schedule — especially the "Compare scheduling options," "How scheduled tasks run," and "Limitations" sections for session-scoped /loop and reminder tasks, plus the resume docs that explain what claude --resume and claude --continue restore.

Current Documentation

The docs currently say:

"Tasks are session-scoped: they live in the current Claude Code process and are gone when you exit. For durable scheduling that survives restarts, use Routines, Desktop scheduled tasks, or GitHub Actions."

"No persistence across restarts. Restarting Claude Code clears all session-scoped tasks."

And the workflow comparison says:

"/loop ... Quick polling while a session is open. Tasks are cancelled when you exit."

What's Wrong or Missing?

Changelog v2.1.110 says:

--resume/--continue now resurrects unexpired scheduled tasks

That changes the documented behavior for session-scoped scheduled tasks. The current docs describe exit/restart as an unconditional end state, but unexpired tasks can now come back when the same session is resumed with claude --resume or claude --continue.

A. The current persistence guidance is now too absolute

The scheduled-tasks docs still say tasks are "gone when you exit" and that restarting Claude Code clears all session-scoped tasks. That no longer describes the full behavior once resume/continue can restore still-valid tasks.

B. The resume docs omit restored task state

Users reading the resume/continue docs are told that conversation history is restored, but not that unexpired scheduled tasks can also be restored when they reopen the same session.

Suggested Improvement

Update the scheduled-task and resume documentation to distinguish between starting a fresh session and resuming an existing one.

Suggested wording direction:

Session-scoped scheduled tasks are still tied to a specific session, but unexpired tasks can be restored when you reopen that session with claude --resume or claude --continue. Expired recurring tasks, already-fired one-shot tasks, and tasks from unrelated sessions are not restored.

Concrete doc updates:

1. Replace unconditional phrases like "gone when you exit" and "Restarting Claude Code clears all session-scoped tasks" with wording that mentions resume/continue restoration.
2. Update the scheduling comparison tables so /loop is not described as simply cancelled on exit without qualification.
3. Add a note to the resume documentation explaining that reopening a session can also bring back that session's unexpired scheduled tasks.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/scheduled-tasks | Primary /loop documentation currently says tasks are gone when you exit and do not persist across restarts |
| https://code.claude.com/docs/en/common-workflows | "Run Claude on a schedule" table says /loop tasks are cancelled when you exit |
| https://code.claude.com/docs/en/how-claude-code-works | Resume section explains what --resume/--continue restore but does not mention scheduled-task restoration |
| https://code.claude.com/docs/en/desktop-scheduled-tasks | Shared scheduling comparison table says /loop is not persistent across restarts and now needs clarification |

Total scope: 4 pages affected

Source: Changelog v2.1.110

Changelog entry: --resume/--continue now resurrects unexpired scheduled tasks