[FEATURE] Allow multiple devices to connect to a single dispatch session

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

Today a Claude Code dispatch session is bound to a single device. I'd like to connect multiple devices to the same dispatch simultaneously — for example, a Mac Mini as the "main" host, with a MacBook and iPhone joining the same session as additional clients.

Use case:

I often kick off a long-running task on my desktop (Mac Mini), then want to:

Check progress or steer the agent from my iPhone while I'm away from the desk. Pick up the same session on my MacBook without losing context or having to start over. Hand off back to the desktop when I'm sitting down again. Right now I either have to start a new session per device, or stay tethered to the one machine where I started.

Proposed behavior:

A dispatch session has one "main" device (where it was started / where the working directory lives) and can accept N additional client devices. Other devices, signed in to the same Anthropic account, can join the session in real time — view streaming output, send input, approve tool calls. Client devices can be desktop (macOS/Windows), mobile (iOS/Android), or web (claude.ai/code)

Things to consider:

1.) Input conflicts:
what happens if two devices send a prompt at the same time? Probably queue them, or lock input to one device at a time with an explicit "take control" handoff.

2.) Tool-call approval:
which device gets prompted? Maybe any connected device can approve, or only the "main."

3.) Pairing/auth: same account is the obvious gate, but per-device approval (similar to adding a new device to iMessage) would be safer than implicit trust of every signed-in device.

4.) Filesystem access: mobile clients obviously can't read local files — they'd be view/steer-only for anything that touches the working directory.

5.) Disconnect behavior: if the main device sleeps or drops, does the session pause, or can a client keep it alive?
Why this matters

The current single-device model assumes you stay at one machine for the duration of a task, which doesn't match how people actually work across desktop/laptop/phone throughout a day.

Proposed Solution

Check at problem.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_