Describe the bug
The --no-remote flag is documented as "Disable remote control of your session from GitHub web and mobile", but it only sets remote to read-only instead of fully disconnecting it. The /remote off slash command correctly disconnects, but --no-remote does not match this behavior.
Affected version
Copilot CLI v1.0.37
Steps to reproduce the behavior
- Launch
copilot --no-remote
- Run
/remote to check status
- Observe:
Remote control status: read-only
Expected behavior
/remote should show Remote control status: disconnected, matching the behavior of /remote off.
Additional context
There is also no persistent setting in ~/.copilot/settings.json to default remote to disconnected, so users must run /remote off manually every session.
Describe the bug
The
--no-remoteflag is documented as "Disable remote control of your session from GitHub web and mobile", but it only sets remote to read-only instead of fully disconnecting it. The /remote off slash command correctly disconnects, but--no-remotedoes not match this behavior.Affected version
Copilot CLI v1.0.37
Steps to reproduce the behavior
copilot --no-remote/remoteto check statusRemote control status: read-onlyExpected behavior
/remoteshould showRemote control status: disconnected, matching the behavior of/remote off.Additional context
There is also no persistent setting in
~/.copilot/settings.jsonto default remote to disconnected, so users must run/remote offmanually every session.