You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
/remote on says "Incoming account connections are disabled" when another CLI on the machine already hosts remote control #5485
Only one CLI process on a machine can host remote control at a time. While another CLI holds the host, /remote on in a second CLI fails with:
Incoming account connections are disabled. Enable them in /environments > Incoming connections before sharing this session.
Incoming connections were already enabled: ahpEnvironment.acceptRemoteConnections was true in ~/.copilot/settings.json, so the message sends the user to turn on a setting that is already on. The real cause was an earlier CLI process, still open, that held the host. While it ran, .attached-host.owner under ~/.copilot/ahp/<compute id>/sessions/ contained that earlier process's ID, and the second CLI never started its host.
After the first CLI exited, /remote on in the second CLI kept failing with the same message. It only worked after the second CLI was restarted.
Affected version
1.0.112
Steps to reproduce the behavior
This is the sequence I observed, not a separate controlled repro:
In CLI A, run /remote on. It succeeds and reports that it is sharing the session.
Keep A open. Start CLI B and run /remote on. It fails with the message above.
Exit A with /exit, then run /remote on in B again. Same message.
Restart B. Its host starts normally.
Expected behavior
The error says another CLI process on this machine is hosting remote control (ideally which one) and how to take over or stop it. Or more than one CLI can host. A CLI that could not host at startup should also pick up the host once it is free, instead of needing a restart.
Activity