Problem
Currently, Claude Code CLI and Claude Desktop Code operate separate scheduled task systems. When configuring a scheduled task in CLI, there's no way to programmatically create a Desktop local scheduled task (or vice versa). Users have to manually copy prompts and settings between the two environments.
Use Case
I set up a daily automated task (a personal reflection diary written to local Obsidian vault). The prompt was crafted in a CLI session, but since it needs local file access, it must run as a Desktop local scheduled task. I had to manually copy the prompt and fill in the Desktop UI form — the CLI couldn't create it directly.
Proposed Solution
Options (any would help):
- Shared scheduled tasks config — CLI and Desktop read from the same task definitions (e.g., a
.claude/scheduled-tasks.json in the project directory), so creating a task in one is visible in the other.
- CLI API for Desktop local tasks — Allow
claude schedule create --local from CLI to register a task that Desktop picks up and runs.
- Cross-environment task management — A unified
/schedule command that can target either local or remote execution.
Environment
- Windows 11, using both Claude Code CLI and Claude Desktop Code
- Tasks involve local file I/O (Obsidian vault), so remote tasks are not an option
Thanks!
Problem
Currently, Claude Code CLI and Claude Desktop Code operate separate scheduled task systems. When configuring a scheduled task in CLI, there's no way to programmatically create a Desktop local scheduled task (or vice versa). Users have to manually copy prompts and settings between the two environments.
Use Case
I set up a daily automated task (a personal reflection diary written to local Obsidian vault). The prompt was crafted in a CLI session, but since it needs local file access, it must run as a Desktop local scheduled task. I had to manually copy the prompt and fill in the Desktop UI form — the CLI couldn't create it directly.
Proposed Solution
Options (any would help):
.claude/scheduled-tasks.jsonin the project directory), so creating a task in one is visible in the other.claude schedule create --localfrom CLI to register a task that Desktop picks up and runs./schedulecommand that can target either local or remote execution.Environment
Thanks!