claude-code - 💡(How to fix) Fix [BUG] remote control [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#50867Fetched 2026-04-20 12:10:51
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

Error Message

The remote interface should continue to relay prompts and confirmations indefinitely, or surface a clear error / terminated-session state if the bridge is broken. Android app appears connected but unresponsive to new input. No error message, no indication of whether a local prompt is pending or the session has crashed.

Error Messages/Logs

Root Cause

When using Remote Control (local CLI session bridged to the Claude Android app), the session worked correctly for several turns — I received multiple permission prompts on the Android app and confirmed each one without issue. After several successful confirmations, the session stalled: the Android app shows the session as still connected, but new prompts produce no response and no tool activity. I suspect a permission prompt or similar interactive state is sitting on the local terminal without being relayed to the remote interface, but I cannot verify this because I am away from the machine.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

What's Wrong?

When using Remote Control (local CLI session bridged to the Claude Android app), the session worked correctly for several turns — I received multiple permission prompts on the Android app and confirmed each one without issue. After several successful confirmations, the session stalled: the Android app shows the session as still connected, but new prompts produce no response and no tool activity. I suspect a permission prompt or similar interactive state is sitting on the local terminal without being relayed to the remote interface, but I cannot verify this because I am away from the machine.

Steps to Reproduce

  1. Start a Remote Control session on the local machine in Terminal (claude --remote-control or /remote-control).
  2. Connect from the Claude Android app.
  3. Send prompts from Android that trigger permission confirmations. Approve each one as it arrives.
  4. After several successful confirmation round-trips, the session stops responding to new prompts from the Android client.

Expected Behavior

The remote interface should continue to relay prompts and confirmations indefinitely, or surface a clear error / terminated-session state if the bridge is broken.

Actual Behavior

Android app appears connected but unresponsive to new input. No error message, no indication of whether a local prompt is pending or the session has crashed.

Environment

  • Claude Code version: latest (will update with exact claude --version output)
  • Local client: Terminal CLI
  • OS: macOS 15 (Sequoia)
  • Hardware: MacBook Pro
  • Remote client: Claude Android app
  • Plan: [Pro / Max]

Additional Context

No --dangerously-skip-permissions flag in use. Session was not in plan mode at the time of the stall. Happy to provide logs or reproduce on request.

What Should Happen?

Remote control client should always show all messages from desktop

Error Messages/Logs

Steps to Reproduce

1 open remote session on Android app 2 receive message prompt from desktop 3 respond

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Latest

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can be potentially resolved by checking for pending permission prompts on the local terminal and ensuring that the remote interface is properly configured to relay prompts and confirmations.

Guidance

  • Verify if there are any pending permission prompts on the local terminal that might be causing the session to stall.
  • Check the Claude Android app settings to ensure that it is configured to receive and display all messages from the desktop, including permission prompts.
  • Try reproducing the issue with the --verbose flag to enable detailed logging, which may help identify the cause of the stall.
  • Consider providing logs or reproducing the issue on request to help diagnose the problem.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be related to the handling of permission prompts or interactive states in the Remote Control session. However, without further information or logs, it is difficult to determine the root cause.

Recommendation

Apply workaround: Check for pending permission prompts on the local terminal and ensure proper configuration of the remote interface, as this may resolve the issue without requiring an upgrade or code changes.

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