[FEATURE] /schedule should support local machine execution, not just remote (CCR)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

/schedule create currently only supports remote execution (CCR) in Anthropic's cloud. The remote agent runs in a sandboxed environment with no access to the local machine, local files, local environment variables, or local services.

Additionally, remote scheduled tasks are limited to a small free-tier allowance, which means your scheduled workflows stop running once the quota resets. There's no way to pay for more or fall back to local execution.

There's no option to schedule a task that runs locally on the user's own machine.

Proposed Solution

Add a new parameter to /schedule create (e.g. --execution local or execution_mode: "local" in the API body) that tells the system to run the scheduled task locally instead of remotely.

How it would work:

1. User creates a trigger with execution_mode: "local" via /schedule create
2. The trigger appears in the Claude Code Desktop app alongside remote triggers, with a clear label distinguishing local vs remote
3. At the scheduled time, the Desktop app spawns a local Claude Code process on the user's machine with full access to local files, env vars, MCP servers, and services
4. The trigger is managed through the same interface: list, update, run now, enable/disable, view logs

The create body would accept a new field:

{
  "name": "My Local Task",
  "cron_expression": "0 9 * * 1-5",
  "execution_mode": "local",
  "job_config": { ... }
}

Where execution_mode is either "remote" (current default, CCR) or "local" (runs on the user's machine via the Desktop app).

Key difference: Local tasks use the user's own API plan (no additional quota restrictions), while remote tasks are subject to the free cloud quota.

Alternative Solutions

• Users can manually set up system cron jobs that invoke the claude CLI, but this bypasses the /schedule UX entirely and doesn't integrate with the trigger management system (list, update, run now, view history, etc.)
• Users can manually create local scheduled tasks through the Claude Code Desktop app UI, but this is tedious compared to the /schedule create command. You lose the ability to script it, version-control your trigger configs, or quickly spin up triggers from the terminal.
• Offering a paid tier for more remote executions solves the quota issue but not the local-access issue

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

• Scheduled agents that run local test suites against uncommitted work
• Agents that interact with local dev databases or Docker containers
• Agents that need local MCP servers not available in the cloud environment
• Agents that need local environment variables (API keys, credentials) that shouldn't leave the machine
• Users who have hit their free cloud quota but still need scheduled tasks to keep running
• All managed from one place in the Claude Code Desktop app, with local and remote triggers side by side

Additional Context

The Claude Code Desktop app is the natural home for local scheduled tasks since it's already a persistent process on the user's machine. It could manage a lightweight scheduler (launchd on macOS, Task Scheduler on Windows) under the hood, while exposing the same /schedule interface for both local and remote triggers. This would make the scheduling feature significantly more useful without requiring users to cobble together their own cron setup.