Feature: Share scheduled tasks between CLI and Desktop

Resolved 💬 2 comments Opened Mar 31, 2026 by theflyelephant Closed May 5, 2026

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):

  1. 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.
  2. CLI API for Desktop local tasks — Allow claude schedule create --local from CLI to register a task that Desktop picks up and runs.
  3. 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!

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗