Remote Control fails on v2.1.63 - "Workspace not trusted" + silent failure
Resolved 💬 3 comments Opened Mar 3, 2026 by JiamanJemma Closed Mar 6, 2026
Bug Description
Remote Control stopped working after updating to v2.1.63. It was working fine a few days ago.
Environment
- Claude Code version: 2.1.63
- OS: macOS (Darwin 25.2.0, Apple Silicon)
- Subscription: Claude Max
- VPN: Active (connecting from outside US)
Symptoms
1. CLI mode: claude remote-control
Returns immediately with:
Error: Workspace not trusted. Please run `claude` in /Users/xxx first to review and accept the workspace trust dialog.
However, running claude in that directory starts a session normally without showing any trust dialog. After that, claude remote-control still gives the same error.
2. In-session mode: /remote-control or /rc
Shows "Remote Control connecting…" briefly, then status bar shows:
Remote Control failed
No additional error details are provided.
Steps to Reproduce
- Update to v2.1.63:
npm update -g @anthropic-ai/claude-code - Run
claude remote-controlfrom home directory → "Workspace not trusted" error - Run
claudein the same directory (session starts fine, no trust dialog shown) - Inside session, run
/remote-control→ "Remote Control failed"
What I Tried
- Running
claudefirst to trigger trust dialog (no dialog appears) npm update -g @anthropic-ai/claude-code- Running from different directories
- Running
claude remote-controlfrom CLI vs/rcinside session - Both fail with different error messages
Expected Behavior
Remote Control should connect and display a session URL / QR code, as it did in the previous version.
Additional Context
- No workspace trust file exists in
~/.claude/directory - No project-level
settings.local.jsonexists - The
settings.local.jsonhas permissions configured but no trust-related settings - 1 MCP server shows "needs auth" in status bar (unrelated Canva OAuth) but unsure if related
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗