Regression (2.1.179–2.1.183): only one local session per machine can be Remote-Controlled at a time

Resolved 💬 2 comments Opened Jun 20, 2026 by hirokikawakami0812-ctrl Closed Jun 20, 2026

What happened

On macOS, I run multiple interactive Claude Code sessions simultaneously, each remote-controlled from the iOS/mobile app (I rely on "remoteControlAtStartup": true so every session auto-registers for Remote Control). Until 2026-06-19 this worked: I could drive 2+ local sessions on the same Mac from the phone at the same time.

After Claude Code auto-updated 2.1.178 → 2.1.183 (on 2026-06-20 ~13:17 JST), only one session on the Mac can be remote-controlled at a time. Starting a second local session breaks Remote Control in the others — they lose the active connection. The remaining session works fine.

Downgrading the same machine back to 2.1.178 fully restored simultaneous multi-session Remote Control (verified — "second session connected" again).

Cross-check

A separate Windows machine, still on an older build, continues to remote-control multiple local sessions at the same time without issue. So this looks like a regression introduced somewhere in 2.1.179 / 2.1.181 / 2.1.182 / 2.1.183 (the versions published after 2.1.178), affecting whether multiple local sessions on one machine can each hold a Remote Control connection concurrently.

Possibly related changelog entries in that range:

  • 2.1.181: "Fixed Remote Control sessions not disconnecting when you sign in to a different account"
  • 2.1.183: "Fixed /remote-control leaving a stale 'connecting…' line..."

Steps to reproduce

  1. On macOS, set "remoteControlAtStartup": true in ~/.claude/settings.json (same account on all sessions).
  2. Update to 2.1.183.
  3. Start session A in one terminal; remote-control it from the mobile app. ✅ works.
  4. Start session B in a second terminal (same account).
  5. Observe: session B claims Remote Control; session A's connection drops. Only one Mac session is remote-controllable at a time.

Expected

Multiple local sessions on the same machine/account can each be remote-controlled concurrently (as in 2.1.178 and as still works on the older Windows build).

Workaround

Pin to 2.1.178 and disable the auto-updater (DISABLE_AUTOUPDATER=1).

Environment

  • Claude Code: regression appears in 2.1.179–2.1.183; last-known-good 2.1.178
  • OS: macOS (Darwin 25.2.0)
  • Install: npm global (~/.npm-global)

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗