/remote-control
Cross-device session sharing — run /remote-control inside Claude to make a session visible on other devices.
/remote-control is a Claude Code slash command. Running it inside a Claude session registers that session for cross-device access — the session then appears in the Hub Console tab on any other device where you open the same environment.
How it works
When a new Claude tab is created in the Hub, the bootstrap sequence automatically sends /remote-control and /rename <sessionName> into the running Claude process via tmux. You don't need to type the command manually — it fires as part of the tab launch.
The registration links the Claude session to the environment's WebSocket channel. Open the same environment's Console tab on another device and the registered session is already there, ready to attach.
Attaching from another device
Open the environment in the Hub on your second device and navigate to the Console tab. The registered session appears as an entry in the tab strip. Clicking it attaches to the same underlying tmux session — same scrollback, same running command.
Use cases
- Phone debugging kick off a long-running Claude task on your laptop, walk away, and watch it complete on your phone
- Agency handoff a developer starts a Claude session investigating a customer issue, and a teammate picks it up on their own device
- On-the-go incident response receive an alert away from your desk and attach to an existing session on your phone instead of pulling out a laptop
Multiple viewers
More than one device can be attached to the same session at the same time. All viewers see the same scrollback and the same live output. Keystrokes from both sides go to the same tmux pane — if two people type at once, both inputs land in sequence. There is no coordination layer beyond what tmux provides natively.
Tab labels and /remote-control
The display label you set by renaming a tab in the Console also propagates to Claude's internal session name via /rename. Sessions registered with /remote-control are identified by this label in the tab strip on other devices. Descriptive labels (checkout-bug, tax-review, on-call-may-12) make it easier to identify which session to attach to when you have multiple running.
Security
Session access is scoped to the environment and your organization. Only members with access to the environment can see and attach to its registered sessions. The session data travels over the same authenticated WebSocket channel used for all Hub real-time features.