Cross-Device Remote Control For Local Machines

Issue 56 Edition 2026-02-25 6 min read

General

Sources: 1 • Confidence: Medium • Updated: 2026-04-13 03:42

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.
Claude Code does not have a documented mechanism for running tasks on a schedule.
A user encountered an error stating remote control was not enabled for their account, and the issue resolved after logging out and back into the Claude Code terminal app.
In remote control, a user reported that the "--dangerously-skip-permissions" flag does not appear to be honored and they had to approve every new action.
A user encountered a failure mode where every prompt returned an API 500 error during a Claude Code remote control session.

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 using 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.

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 Cowork scheduled 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.

A user encountered an error stating remote control was not enabled for their account, and the issue resolved after logging out and back into the Claude Code terminal app.
A user encountered a failure mode where every prompt returned an API 500 error during a Claude Code remote control session.
Restarting the program on the host machine can cause existing Claude Code remote sessions to return unclear API errors rather than clearly indicating that the session has terminated.

In remote control, a user reported that the "--dangerously-skip-permissions" flag does not appear to be honored and they had to approve every new action.

What is the official specification for remote control permissions, including whether permission-bypass flags are intended to apply to remote sessions?
How prevalent are the reported API 500 errors and entitlement/authentication issues across users, environments, and versions?
What are the failure and recovery semantics when the host machine or host process restarts during a remote control session, and are clients notified with explicit session-termination messaging?
Are there any official scheduling capabilities planned or available for Claude Code itself, beyond what is documented, and what is the intended division of responsibilities between Claude Code and Cowork?
What timing guarantees and catch-up rules apply to Cowork scheduled tasks beyond the described skip-and-run-on-resume behavior (for example, multiple missed runs, ordering, or concurrency)?

Cross-device remote control in Claude Code could indicate expansion toward multi-client developer workflows, raising expectations for broader session management and orchestration features beyond single-machine use.
The split where Cowork handles scheduling while Claude Code lacks it suggests a product boundary that may shape monetization and packaging if remote control becomes a core workflow that benefits from paid automation layers.
Reported entitlement glitches, API 500 errors, and unclear session termination after restarts suggest early-stage reliability gaps that could slow adoption until robustness and lifecycle semantics improve.

Official documentation clarifying remote control permissions, whether bypass flags apply to remote sessions, and explicit session lifecycle behaviors including restart handling and termination messaging.
Evidence of improved reliability such as fewer API 500 failures and fewer entitlement or authentication issues, plus clearer recovery flows during remote sessions.
Product updates that add scheduling to Claude Code or explicitly expand Cowork capabilities and guarantees, indicating a deliberate roadmap for automation and orchestration.

Persistent or widespread API 500 errors or entitlement failures that remain unresolved across versions, making remote sessions unreliable for routine workflows.
Documentation or product behavior that explicitly enforces per-action approvals in remote control with no supported unattended mode, limiting automation use cases.
No progress on session management constraints such as one session per machine, unclear termination, and poor restart recovery, reducing practical cross-device utility.