claude-code - 💡(How to fix) Fix Remote sessions need desktop↔mobile continuity and consistent permissions [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#57821Fetched 2026-05-11 03:24:29
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

Root Cause

The whole pitch of remote / mobile sessions is being able to drive Claude from anywhere. If every action requires me to tap "approve" on my phone, I'm worse off than if I'd just stayed at the desk — and the inconsistency between desktop (silent) and mobile (modal-on-everything) for the same configured permissions makes it feel broken, not safe.

If `bypassPermissions` is intentionally disabled in remote for safety reasons, please surface that explicitly in `/doctor` or settings docs. As-is, the setting looks like it should work everywhere and silently doesn't.

RAW_BUFFERClick to expand / collapse

What I want

I'm a daily Claude Code desktop user (macOS). Two pieces of feedback on remote / claude.ai mobile sessions:

  1. Session continuity. I want to start a session in the Claude Code desktop app and pick it up on my phone — keep the same conversation, history, and context. Today the only path I've found is launching a fresh remote session via the claude remote-control daemon + claude.ai/code, which is a separate session, not a continuation. I don't want to use the CLI to bridge devices; I want the desktop app and mobile to be two views into the same session.

  2. Consistent permission experience across devices. My `~/.claude/settings.json` has: ```json "permissions": { "defaultMode": "bypassPermissions", "allow": [ ... ] }, "skipDangerousModePermissionPrompt": true ``` On the desktop app: zero permission prompts, exactly as configured. On a fresh remote session (claude.ai/code from mobile): permission modal on nearly every tool call. `bypassPermissions` appears to be silently ignored remotely, and explicit `allow` entries don't match because remote invokes MCP tools under a UUID-prefixed name (`mcp__<uuid>__save_issue`) rather than the human-readable name (`mcp__claude_ai_Linear__save_issue`) that the desktop uses for the same MCP server.

Why this matters

The whole pitch of remote / mobile sessions is being able to drive Claude from anywhere. If every action requires me to tap "approve" on my phone, I'm worse off than if I'd just stayed at the desk — and the inconsistency between desktop (silent) and mobile (modal-on-everything) for the same configured permissions makes it feel broken, not safe.

If `bypassPermissions` is intentionally disabled in remote for safety reasons, please surface that explicitly in `/doctor` or settings docs. As-is, the setting looks like it should work everywhere and silently doesn't.

Net result

I've disabled remote control entirely (`disableRemoteControl: true`) and killed the daemon. I'd love to re-enable when these are addressed.

Environment

  • macOS (Darwin 25.4.0)
  • Claude Code via Homebrew (`/opt/homebrew/bin/claude`)
  • Linear MCP server (HTTP transport at `https://mcp.linear.app/mcp\`)

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Remote sessions need desktop↔mobile continuity and consistent permissions [1 comments, 2 participants]