Preflight Checklist
Problem Statement
Task configuration for scheduled tasks is currently split across two locations:
~/.claude/scheduled-tasks/{taskId}/SKILL.md — task prompt (persistent, user-managed)
~/Library/Application Support/Claude/claude-code-sessions/{uuid}/{uuid}/scheduled-tasks.json — everything else (session storage, volatile)
The scheduled-tasks.json contains critical configuration that is not recoverable if the session directory is lost:
json { "id": "my-task", "cronExpression": "*/30 9-20 * * 1-5", "enabled": true, "model": "claude-sonnet-4-6", "cwd": "/path/to/project", "permissionMode": "acceptEdits", "approvedPermissions": [ { "toolName": "Bash" }, { "toolName": "Read" } ] }
The session directory path contains UUIDs that can change or be deleted when:
When this happens, only the SKILL.md prompt survives. All scheduling, permission, and runtime settings are lost silently.
Proposed Solution
Store all task configuration alongside SKILL.md in ~/.claude/scheduled-tasks/{taskId}/:
~/.claude/scheduled-tasks/my-task/
SKILL.md ← prompt (already here)
task.json ← cronExpression, enabled, model, cwd, permissionMode, approvedPermissions (proposed)
This would make the full task definition:
Alternative Solutions
Manually back up scheduled-tasks.json after any configuration change.
Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
Use Case Example
- I set up several scheduled tasks with specific cron schedules, models,
and "always allow" tool permissions.
- Claude Desktop is reinstalled or session data is reset.
- The SKILL.md prompts survive, but all scheduling and permission settings
are gone with no warning.
- Every task must be manually reconfigured from scratch before autonomous
execution can resume.
Additional Context
Preflight Checklist
Problem Statement
Task configuration for scheduled tasks is currently split across two locations:
~/.claude/scheduled-tasks/{taskId}/SKILL.md— task prompt (persistent, user-managed)~/Library/Application Support/Claude/claude-code-sessions/{uuid}/{uuid}/scheduled-tasks.json— everything else (session storage, volatile)The
scheduled-tasks.jsoncontains critical configuration that is not recoverable if the session directory is lost:
json { "id": "my-task", "cronExpression": "*/30 9-20 * * 1-5", "enabled": true, "model": "claude-sonnet-4-6", "cwd": "/path/to/project", "permissionMode": "acceptEdits", "approvedPermissions": [ { "toolName": "Bash" }, { "toolName": "Read" } ] } The session directory path contains UUIDs that can change or be deleted when:
When this happens, only the SKILL.md prompt survives. All scheduling, permission, and runtime settings are lost silently.
Proposed Solution
Store all task configuration alongside SKILL.md in
~/.claude/scheduled-tasks/{taskId}/:~/.claude/scheduled-tasks/my-task/
SKILL.md ← prompt (already here)
task.json ← cronExpression, enabled, model, cwd, permissionMode, approvedPermissions (proposed)
This would make the full task definition:
Alternative Solutions
Manually back up scheduled-tasks.json after any configuration change.
Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
Use Case Example
and "always allow" tool permissions.
are gone with no warning.
execution can resume.
Additional Context