[FEATURE] Unify Dispatch / Remote Control / Channels into a single "task" model

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

Currently, Claude Code offers three overlapping ways to run sessions remotely (Dispatch, Remote Control, Channels), each with different entry points and setup steps. From a user perspective, the underlying need is the same: "run Claude on my machine when I'm not at the terminal."

Suggestion: unify these into a single task-queue model where any trigger source (mobile, external event, schedule) enqueues a task, Claude executes it locally, and results are delivered back through a unified notification channel. The current split feels like an implementation distinction rather than a user-facing one, and adds unnecessary mental overhead when choosing the right feature.

Proposed Solution

Currently, Claude Code offers three overlapping ways to run sessions remotely (Dispatch, Remote Control, Channels), each with different entry points and setup steps. From a user perspective, the underlying need is the same: "run Claude on my machine when I'm not at the terminal."

Suggestion: unify these into a single task-queue model where any trigger source (mobile, external event, schedule) enqueues a task, Claude executes it locally, and results are delivered back through a unified notification channel. The current split feels like an implementation distinction rather than a user-facing one, and adds unnecessary mental overhead when choosing the right feature.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_