Remote Control: `Session creation failed` regression — was working, now fails 3× on enable (macOS, v2.1.193)

[hyeon3125-dev]

Summary

Enabling Remote Control on a local session was working, then started failing consistently with Session creation failed — see debug log. Same machine, same local session, 3 consecutive failed attempts. When it did work earlier, taking the session over from the mobile app also tended to auto-archive the desktop session and drop the connection (I never archived manually) — but the hard, reproducible failure now is that remote control can't be enabled at all.

This looks like a regression (worked 06-28 and 06-29 00:06, fails from 06-29 13:31 onward) on the remote bridge / session-creation path, not an auth or version issue.

Environment

• Claude Code CLI v2.1.193
• macOS (Darwin 25.5.0), Apple Silicon Mac mini
• Plan: Max
• Auth: claude.ai OAuth (logged in, confirmed working — model calls succeed normally)
• claude remote-control previously connected fine from the same machine/account

Steps to reproduce

1. Have an active local Claude Code session.
2. Toggle Enable Remote Control for that session.
3. Bridge reaches failed — Session creation failed — see debug log; remote control never enables.
4. Retrying immediately reproduces the same failure (3/3 here).

(Earlier, when enabling succeeded: opening the session from the Claude mobile app to take it over moved the desktop session to Archive and dropped the connection, without any manual archive action.)

Expected

• Enabling Remote Control creates the remote session and reaches connected.
• Handing the live session to mobile keeps it active (per docs: "conversation stays in sync across all connected devices"), not auto-archived/disconnected.

Actual

• bridge_state: failed — Session creation failed on every enable attempt.

Log evidence (~/Library/Logs/Claude/claude.ai-web.log, sanitized)

Worked earlier — same local session local_748d8400-…:

2026-06-29 00:06:01 [info] Enabling remote control for session local_748d8400-…
2026-06-29 00:06:02 [info] [remote-control] bridge_state: ready
2026-06-29 00:06:02 [info] Remote control enabled: https://claude.ai/code/session_01Ug…(redacted)
2026-06-29 00:06:02 [info] [remote-control] bridge_state: connected
2026-06-29 00:23:06 [info] handoff: publishing session_01Ug…(redacted)
2026-06-29 00:36:21 [info] handoff: publishing session_01Ug…(redacted)

Then started failing — same local session, 3 consecutive attempts:

2026-06-29 13:31:09 [info] Enabling remote control for session local_748d8400-…
2026-06-29 13:31:11 [info] [remote-control] bridge_state: failed — Session creation failed — see debug log
2026-06-29 13:31:11 [error] Failed to toggle remote control for local_748d8400-…: Session creation failed — see debug log
2026-06-29 13:36:31 [info] [remote-control] bridge_state: failed — Session creation failed — see debug log
2026-06-29 13:40:30 [info] [remote-control] bridge_state: failed — Session creation failed — see debug log

Notes / things already ruled out

• Not auth — claude.ai OAuth is valid; normal model calls work.
• Not version — v2.1.193 (well above the remote-control minimum).
• Not plan — Max tier.
• It is a state/regression: identical local session id transitioned from connected to Session creation failed within the same day with no config changes on my side.
• The error references a "debug log"; if there's a more specific remote-bridge debug log path beyond claude.ai-web.log, point me to it and I'll attach the corresponding lines.

Happy to provide more logs or run a specific diagnostic.

[github-actions]

Found 3 possible duplicate issues:

1. Remote Control no longer available — was previously working #72124
2. Remote Control (/rc) stuck on "connecting…" — bridge sends source field rejected by ccr-byoc session-create schema (400) #68856
3. [BUG] Remote Control bridge enters terminal "failed" state after JWT refresh 401 — never retries; concurrent-session token-refresh race triggers it #67360

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #72124.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code