Support durable local scheduled tasks from the CLI

Problem

There's currently no way to create durable local scheduled tasks from the Claude Code CLI. The available options are:

1. CronCreate — session-only, dies when the session ends, auto-expires after 7 days
2. Remote triggers (RemoteTrigger) — runs in Anthropic's cloud, so it has no access to local filesystem, credentials, caches, or Dropbox

For users running automation pipelines that depend on local data (credential files, local caches, Dropbox sync directories, etc.), neither option works for persistent scheduling. The only way to create durable scheduled tasks is through the Cowork web interface, which requires a context switch away from the CLI.

Current workaround

Document the task in CLAUDE.md and hope a future Cowork session picks it up — fragile and manual.

Proposed solution

A CLI-accessible mechanism to create scheduled tasks that:

• Persist to disk (survive session restarts and machine reboots)
• Execute locally (not in a remote cloud sandbox) — with access to the local filesystem, env vars, and credentials
• Follow cron syntax for scheduling
• Are managed from the CLI (create, list, update, delete)

Essentially: CronCreate but with durable: true actually writing to disk and being picked up by a local daemon/agent, rather than being session-scoped.

Use case

I run 20+ automation pipelines (Reddit monitoring, X brand scanning, transaction analysis, cost tracking, blog drafting, etc.) that all read from ~/.config/*/credentials.json, write to ~/Library/CloudStorage/Dropbox/..., and maintain caches in ~/.cache/. These can't run remotely. Every time I build a new pipeline, I have to leave the CLI to schedule it through the web UI.