[DOCS] Desktop scheduled tasks docs omit one-shot task behavior

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

Desktop scheduled task frequency options and one-shot task lifecycle

Current Documentation

The docs currently frame Desktop scheduled tasks as recurring-only:

# Schedule recurring tasks in Claude Code Desktop By default, scheduled tasks start a new session automatically at a time and frequency you choose. Use them for recurring work like daily code reviews, dependency update checks, or morning briefings that pull from your calendar and inbox. Manual: no schedule, only runs when you click Run now. Useful for saving a prompt you trigger on demand Hourly: runs every hour. Each task gets a fixed offset of up to 10 minutes from the top of the hour to stagger API traffic Daily: shows a time picker, defaults to 9:00 AM local time Weekdays: same as Daily but skips Saturday and Sunday * Weekly: shows a time picker and a day picker

No one-shot or run-once scheduled task option is documented on this page.

What's Wrong or Missing?

Changelog v2.1.105 includes this entry:

Fixed one-shot scheduled tasks re-firing repeatedly when the file watcher missed the post-fire cleanup

That release note shows Claude Code has a one-shot scheduled task mode that should fire once and then clean itself up. But the Desktop scheduled tasks docs only describe recurring frequencies plus Manual mode.

What's missing:

A. One-shot task creation

There is no documentation for creating a scheduled task that runs once at a specific time.

B. Post-run behavior

There is no documentation that a one-shot task should remove or disable itself after firing.

C. Troubleshooting expectations

Because the feature is undocumented, users have no baseline for recognizing that repeated firing was a bug fixed in v2.1.105 rather than intended behavior.

Suggested Improvement

Add a one-shot scheduled task option to the Desktop scheduled tasks docs.

Suggested content:

1. In Frequency options, document a One-time / Run once mode (or document the conversational flow if one-shot tasks are only created that way today).
2. Explain that the task fires once at the chosen time and then removes or disables itself after the run completes.
3. Clarify how one-shot tasks differ from Manual tasks, which never run automatically.
4. In Manage scheduled tasks, mention what users should expect to see after a one-shot task fires (for example, archived history but no future runs).

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/desktop-scheduled-tasks | Primary documentation page; currently presented as recurring-only and the frequency list omits one-shot behavior |
| https://code.claude.com/docs/en/overview | "Schedule recurring tasks" overview card also describes scheduled tasks as recurring automation |
| https://code.claude.com/docs/en/common-workflows | "Run Claude on a schedule" section describes recurring scheduled work and links users to Desktop scheduled tasks |

Total scope: 3 pages affected

Source: Changelog v2.1.105

Exact changelog entry: Fixed one-shot scheduled tasks re-firing repeatedly when the file watcher missed the post-fire cleanup