Claude Code Remote Control: New Cross-Device Capability And Activation Path

Issue 56 Edition 2026-02-25 7 min read

General

Sources: 1 • Confidence: High • Updated: 2026-03-02 19:32

Key takeaways

Claude Code supports starting a remote control session on a computer and sending prompts to it from Claude Code web interfaces including web, iOS, and the native desktop app.
The author reported seeing an error that remote control was not enabled for their account despite being their own administrator, and the issue resolved after logging out and back into the Claude Code terminal app.
Claude Code does not have a documented mechanism for running tasks on a schedule.
The author hopes Anthropic is developing a Cowork Cloud product.
In Claude Code remote control sessions, the author reported needing to approve every new action and reported that remote control did not appear to honor the "--dangerously-skip-permissions" flag.

Claude Code supports starting a remote control session on a computer and sending prompts to it from Claude Code web interfaces including web, iOS, and the native desktop app.
A Claude Code remote control session can be started from the command line with the command "claude remote-control".
After upgrading the Claude iOS app, a remote session can appear in the app as "Remote Control Session (Mac)" under the Code tab.
Only one Claude Code remote control session can run on a machine at a time.

The author reported seeing an error that remote control was not enabled for their account despite being their own administrator, and the issue resolved after logging out and back into the Claude Code terminal app.
The author reported a failure mode during a remote control session where every prompt returned an API 500 error.
The author reported that restarting the program on the machine can cause existing remote sessions to return API errors instead of clearly indicating that the session has terminated.

Claude Code does not have a documented mechanism for running tasks on a schedule.
Anthropic announced scheduled recurring tasks in Cowork, described as Claude Code's general agent sibling.
Cowork scheduled tasks run only while the computer is awake and the Claude Desktop app is open; if a run is missed due to sleep or the app being closed, it is skipped and then executed automatically once the computer wakes or the app is opened again.

The author hopes Anthropic is developing a Cowork Cloud product.
The author expects the current Claude Code remote control issues to be fixed relatively quickly.

In Claude Code remote control sessions, the author reported needing to approve every new action and reported that remote control did not appear to honor the "--dangerously-skip-permissions" flag.

What is the actual rollout/availability scope of Claude Code remote control (accounts, regions, plans), and is enablement controlled by an entitlement flag?
What are the primary causes and incidence rates of remote control API 500 errors, and are they correlated with specific clients, session duration, or backend incidents?
What is the intended lifecycle behavior for remote sessions when the host program restarts, and should clients receive explicit termination signaling?
Is "--dangerously-skip-permissions" designed to apply to remote control sessions, and if so, is its current behavior a bug or a policy restriction?
Are there any official Claude Code scheduling capabilities (APIs, integrations, or planned features) beyond what is currently documented?

Cross device remote control in Claude Code could increase engagement for Anthropic developer tooling if rollout is broad and reliable, creating potential demand for higher tier plans tied to remote workflows.
Operational friction suggests the feature may be in early rollout with entitlement gating, implying near term support load and potential near term improvements that could change user adoption trajectory.
Per action approvals and apparent non support for permission skipping may limit unattended automation, implying the product positioning may be interactive assistance rather than full automation unless permissions evolve.

Official documentation or release notes clarifying availability scope by region and plan, plus explicit mention of any entitlement enablement for remote control.
Improved reliability indicators such as fewer remote control API 500 reports and clearer session termination behavior when the host restarts.
Product updates that add scheduling or cloud execution, or explicitly announce a cloud hosted Cowork direction, aligning with user hopes for Cowork Cloud.

Remote control remains limited to narrow accounts or is quietly rolled back, with persistent enablement errors and no clear rollout communication.
Ongoing high incidence of API 500 failures or confusing lifecycle behavior that discourages routine use across clients.
Explicit policy that remote sessions always require per action approval and that permission skipping will not apply, limiting automation use cases and reducing expected adoption for unattended workflows.