Code tab: sessions sync only one direction across devices on the same account
Summary
Two Macs signed into the same individual account with a single personal workspace. Code-tab session visibility works in one direction only:
- On Machine B (Mac Mini) I can see Machine A (MacBook)'s Code sessions. ✅
- On Machine A (MacBook) I cannot see any of Machine B (Mac Mini)'s Code sessions. ❌
Environment
- Two Apple Silicon Macs, same individual account, single personal workspace (no org switching involved)
- Reporting machine (MacBook): Claude desktop Code
2.1.160, VM2.1.156, macOS 26.3.1 (build 25D771280a)
Steps / what I observe
- Sign both machines into the same account.
- Enable "Enable remote control by default" (Settings → Claude Code) on both.
- Restart the apps; start new sessions on each machine.
- From the Mac Mini, the MacBook's sessions appear in the Code tab. From the MacBook, the Mac Mini's sessions never appear.
Ruled out
- ✅ "Enable remote control by default" is checked on both machines.
- ✅ Both machines awake, online, app running at the same time.
- ✅ New sessions created on the Mac Mini after enabling the toggle and restarting still don't appear (so it isn't a "new-sessions-only" gap).
- ✅ Single personal workspace on both — no workspace/org mismatch.
- ✅ Same account/login on both.
Technical detail
On the machine whose sessions are visible to the other (the MacBook), ~/Library/Application Support/Claude/bridge-state.json shows an active bridge: "enabled": true, "userConsented": true with a populated remoteSessionId/environmentId. The non-visible machine's sessions never surface, which suggests its bridge isn't registering server-side despite remote control being enabled.
Expected
With remote control enabled on all devices of one account, Code-tab sessions should be visible bidirectionally across those devices.
Actual
One-directional visibility only; the second machine's sessions never appear on the first.
Possibly related
Same app, session-handling problems: #64743
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗