bug : Remote Control: /rc loops "connecting… → disconnected", never reaches Connected (Windows 11, Pro)

Resolved 💬 1 comment Opened Jun 12, 2026 by jerome44400 Closed Jun 12, 2026

Preflight Checklist

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

What's Wrong?

Remote Control: /rc loops "connecting… → disconnected", never reaches Connected (Windows 11, Pro)

Bug Description

Running /remote-control (bare command, fresh session) never completes the
handshake. It shows /rc connecting… then falls back to
Remote Control disconnected, in a loop. It never reaches Connected/Attached.
As a result, messages sent from the mobile app / browser are marked "read" but
never reach the local session — the terminal stays completely silent.

Environment

  • OS: Windows 11
  • Claude Code: 2.1.175
  • Plan: Claude Pro
  • Model: Fable 5
  • Auth: OAuth (firstParty), logged in successfully

Steps to Reproduce

  1. Start a fresh claude session
  2. Run /remote-control (bare, no session name)
  3. Output shows /rc connecting…
  4. Shortly after: Remote Control disconnected
  5. Repeats on every retry — never reaches Connected

What I Ruled Out

  • Claude Code is on the latest version (2.1.175)
  • Test-NetConnection api.anthropic.com -Port 443 → TcpTestSucceeded: True
  • No ANTHROPIC_BASE_URL set at Process / User / Machine level
  • No stray ANTHROPIC_API_KEY
  • PATH intact (System32 present)
  • No outbound firewall rule blocking node.exe
  • Fresh session, no stacked / ghost Remote Control sessions
  • Tested on Wi-Fi, 4G and 5G
  • Tested from Android app, desktop app, and browser — same result

Expected Behavior

/remote-control should reach Connected/Attached and deliver remote
messages to the local session.

Actual Behavior

/rc connecting…Remote Control disconnected, looping. Remote messages
never delivered. Terminal shows zero activity.

Note

Remote Control launched for Max first, with Pro access rolling out gradually and
still in research preview. Possibly the Pro-tier handshake isn't fully enabled
server-side for this account?

Related: #38049 (same family of symptom on Windows).

What Should Happen?

i want controle claude code with my tel

Error Messages/Logs

Steps to Reproduce

Remote Control: /rc loops "connecting… → disconnected", never reaches Connected (Windows 11, Pro)

Bug Description

Running /remote-control (bare command, fresh session) never completes the
handshake. It shows /rc connecting… then falls back to
Remote Control disconnected, in a loop. It never reaches Connected/Attached.
As a result, messages sent from the mobile app / browser are marked "read" but
never reach the local session — the terminal stays completely silent.

Environment

  • OS: Windows 11
  • Claude Code: 2.1.175
  • Plan: Claude Pro
  • Model: Fable 5
  • Auth: OAuth (firstParty), logged in successfully

Steps to Reproduce

  1. Start a fresh claude session
  2. Run /remote-control (bare, no session name)
  3. Output shows /rc connecting…
  4. Shortly after: Remote Control disconnected
  5. Repeats on every retry — never reaches Connected

What I Ruled Out

  • Claude Code is on the latest version (2.1.175)
  • Test-NetConnection api.anthropic.com -Port 443 → TcpTestSucceeded: True
  • No ANTHROPIC_BASE_URL set at Process / User / Machine level
  • No stray ANTHROPIC_API_KEY
  • PATH intact (System32 present)
  • No outbound firewall rule blocking node.exe
  • Fresh session, no stacked / ghost Remote Control sessions
  • Tested on Wi-Fi, 4G and 5G
  • Tested from Android app, desktop app, and browser — same result

Expected Behavior

/remote-control should reach Connected/Attached and deliver remote
messages to the local session.

Actual Behavior

/rc connecting…Remote Control disconnected, looping. Remote messages
never delivered. Terminal shows zero activity.

Note

Remote Control launched for Max first, with Pro access rolling out gradually and
still in research preview. Possibly the Pro-tier handshake isn't fully enabled
server-side for this account?

Related: #38049 (same family of symptom on Windows).

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

opus 4.8

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗