Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /remote-control: mobile session locked out when desktop has an unanswered permission prompt [1 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#55619•Fetched 2026-05-03 04:48:44
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
spragginsdesignsspragginsdesigns
Participants
spragginsdesignsspragginsdesigns
Timeline (top)
labeled ×5

When using /remote-control from the mobile app, if the desktop session is sitting on a tool-use permission prompt (the "Allow once / Allow for session / Deny" picker) that you didn't answer before switching devices, the remote session is effectively frozen. Mobile lets you keep typing and queueing messages, but none of them deliver, and there is no way to surface or respond to the pending permission prompt from mobile. The only recovery is to physically return to the desktop machine, hit Esc, and re-issue the prompt.

Root Cause

When using /remote-control from the mobile app, if the desktop session is sitting on a tool-use permission prompt (the "Allow once / Allow for session / Deny" picker) that you didn't answer before switching devices, the remote session is effectively frozen. Mobile lets you keep typing and queueing messages, but none of them deliver, and there is no way to surface or respond to the pending permission prompt from mobile. The only recovery is to physically return to the desktop machine, hit Esc, and re-issue the prompt.

RAW_BUFFERClick to expand / collapse

Summary

When using /remote-control from the mobile app, if the desktop session is sitting on a tool-use permission prompt (the "Allow once / Allow for session / Deny" picker) that you didn't answer before switching devices, the remote session is effectively frozen. Mobile lets you keep typing and queueing messages, but none of them deliver, and there is no way to surface or respond to the pending permission prompt from mobile. The only recovery is to physically return to the desktop machine, hit Esc, and re-issue the prompt.

Steps to reproduce

  1. On desktop, start a task that will trigger a tool-use permission prompt (e.g. an Edit/Write to a path that isn't pre-allowed).
  2. Before answering the "Allow once / Allow for session / Deny" prompt, walk away from the desktop and open the Claude mobile app.
  3. Open the same session via /remote-control (Desktop 2 in my case).
  4. Type any follow-up messages from mobile (e.g. "I approve continue", "continue").

Expected

Mobile should either:

  • Surface the pending permission prompt with the same Allow once / Allow for session / Deny choices so the remote user can unblock the session, or
  • Show a clear "session is blocked on a permission prompt on the desktop client — cannot proceed remotely" state instead of silently queueing input.

Actual

  • The pending permission prompt is invisible on mobile.
  • Messages typed on mobile appear to send but stack behind the unanswered prompt and never get processed.
  • Session stays frozen until you return to the desktop, press Esc to dismiss the prompt, and resubmit.

Impact

This defeats a big chunk of the value of /remote-control — any task that hits a tool needing approval will brick the remote session, and the user has no signal from the mobile UI that this is what happened. Easy to lose work or waste time waiting on a session that will never resume.

Environment

  • Claude Code CLI on Windows 11 (desktop side, PowerShell)
  • Claude mobile app (iOS) using /remote-control
  • Tool was a Write/Edit to a project file that wasn't on the auto-allow list

Suggested fix direction

Either forward the pending permission prompt to the remote-control client, or have the desktop auto-reject queued input from a remote client while a permission prompt is pending and surface that state on mobile.

extent analysis

TL;DR

Implement a mechanism to forward pending permission prompts to the remote-control client or auto-reject queued input from the remote client while a prompt is pending.

Guidance

  • Identify the current implementation of permission prompts in the desktop application and determine how to extend it to forward prompts to the remote-control client.
  • Consider adding a state machine to track the status of permission prompts and handle incoming remote-control input accordingly.
  • Develop a UI component in the mobile app to display pending permission prompts and allow users to respond to them.
  • Investigate the feasibility of auto-rejecting queued input from the remote client while a permission prompt is pending and displaying a corresponding state on the mobile app.

Example

# Pseudo-code example of forwarding permission prompts to remote-control client
def handle_permission_prompt(prompt):
    # Check if remote-control client is connected
    if remote_client_connected:
        # Forward prompt to remote-control client
        send_prompt_to_remote_client(prompt)
    else:
        # Handle prompt locally
        handle_prompt_locally(prompt)

Notes

The suggested fix direction requires modifications to both the desktop application and the mobile app. The implementation details may vary depending on the specific technologies and frameworks used.

Recommendation

Apply a workaround by displaying a clear "session is blocked on a permission prompt on the desktop client — cannot proceed remotely" state on the mobile app when a permission prompt is pending, to prevent users from queuing input that will not be processed. This can be done while working on the long-term solution of forwarding permission prompts to the remote-control client.

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…
#api#ssr#installation#tensor shape#autograd error

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-control: mobile session locked out when desktop has an unanswered permission prompt [1 participants]