Anthropic launches Claude Code Remote Control for device automation
Anthropic has released Claude Code Remote Control, a new feature allowing users to initiate remote control sessions on their computers and manage them via Claude Code on web, iOS, and native apps. The feature is in early stages with reported stability issues including API 500 errors and permission approval requirements.
Anthropic Adds Device Control to Claude Code
Anthropichas released Claude Code Remote Control, enabling users to execute commands on their computers via Claude Code interfaces across web, iOS, and desktop applications. The feature allows users to start a remote session locally using the claude remote-control command, then send instructions from any Claude Code interface to that running session.
How It Works
Users initialize the feature by running claude remote-control in their Claude Code terminal. The session appears across connected devices—for example, the iOS app displays it as "Remote Control Session (Mac)" in the Code tab. However, only one active session per machine is currently supported.
Early Implementation Issues
The feature exhibits significant stability problems in its initial release:
- Authentication friction: Initial access attempts returned "Remote Control is not enabled for your account" errors, requiring logout and re-login to function
- API errors: Users encounter mysterious HTTP 500 errors, particularly after restarting the local daemon, with no graceful error messaging
- Permission approval: The feature does not support the
--dangerously-skip-permissionsflag, forcing manual approval of every action - No graceful session termination: Restarting the local program causes existing sessions to fail with API errors rather than clean disconnection messages
A demonstration attempt to play music via AppleScript resulted in a 500 error despite the assistant generating correct command syntax.
Feature Gaps vs. Competitors
Claude Code Remote Control currently lacks two critical features found in competing tools like OpenClaw:
- Cross-device initiation: Cannot trigger commands directly from mobile without establishing a prior local session
- Scheduled execution: No documented mechanism for running tasks on a schedule
Technical Details
The feature integrates with Claude Code's existing interface but relies on local daemon processes. Session IDs follow the format "Mac:dev:[identifier]" for device identification.
What This Means
Claude Code Remote Control represents Anthropic's direct entry into the agentic device-control category, positioning Claude against tools like OpenClaw that already offer mobile-initiated automation. The early instability suggests this is a rapid internal release, likely to receive fixes within weeks. The missing scheduled execution capability is notable—it's the differentiator that makes competing "Claw" tools genuinely useful for repetitive tasks rather than just novelties. Success here depends on whether Anthropic closes the stability gaps and adds scheduled task support before competitors solidify market position.