claude-code - 💡(How to fix) Fix Remote Control session becomes unresponsive after first command from mobile app [3 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#52796Fetched 2026-04-25 06:20:42
View on GitHub
Comments
3
Participants
2
Timeline
7
Reactions
0
Timeline (top)
commented ×3labeled ×3cross-referenced ×1

After activating /remote-control from an existing Claude Code session on Linux and pairing the mobile Claude app, the session becomes unresponsive after the first command sent from mobile. The "working" spinner (bamboozling, clauding, etc.) is shown briefly, then disappears with no output on either device. Subsequent messages also trigger the spinner but produce no response.

Root Cause

After activating /remote-control from an existing Claude Code session on Linux and pairing the mobile Claude app, the session becomes unresponsive after the first command sent from mobile. The "working" spinner (bamboozling, clauding, etc.) is shown briefly, then disappears with no output on either device. Subsequent messages also trigger the spinner but produce no response.

Fix Action

Workaround

Kill the session and restart claude + /remote-control.

RAW_BUFFERClick to expand / collapse

Description

After activating /remote-control from an existing Claude Code session on Linux and pairing the mobile Claude app, the session becomes unresponsive after the first command sent from mobile. The "working" spinner (bamboozling, clauding, etc.) is shown briefly, then disappears with no output on either device. Subsequent messages also trigger the spinner but produce no response.

Environment

  • Claude Code version: 2.1.119
  • Plan: Max
  • OS: Linux (Ubuntu 5.15.0-174-generic)
  • Auth: claude.ai account (not API key)
  • Mobile: Claude app

Steps to reproduce

  1. On Linux server, run claude in a project directory
  2. Type /remote-control — session activates, URL shown (no QR code displayed)
  3. Open the session from the Claude mobile app — chat history visible on both devices
  4. Send a command from mobile
  5. Spinner appears, then disappears with no response
  6. Send another simple message like "hello" — same behavior

Expected

The assistant response should render on both PC terminal and mobile app.

Actual

No output rendered on either device. Session appears hung.

Workaround

Kill the session and restart claude + /remote-control.

extent analysis

TL;DR

The issue can likely be resolved by killing the current session and restarting claude with the /remote-control command.

Guidance

  • Verify that the issue persists across different commands sent from the mobile app to isolate if it's command-specific or a general communication issue.
  • Check for any updates to the Claude Code version or the mobile app, as updates might address known issues.
  • When restarting claude and /remote-control, ensure that any background processes from previous sessions are properly terminated to prevent interference.
  • Consider testing the /remote-control feature with a different project or a minimal setup to see if the issue is project-specific.

Example

No specific code snippet is applicable in this scenario as the issue seems related to the interaction between the Claude Code session and the mobile app.

Notes

The provided workaround of killing the session and restarting claude with /remote-control suggests a potential issue with session management or communication handshake between the devices. However, without more detailed logs or error messages, it's challenging to pinpoint the exact cause.

Recommendation

Apply the workaround of killing the session and restarting claude with /remote-control, as it has been reported to temporarily resolve the issue, allowing for continued use of the feature until a more permanent fix is available.

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