--no-remote flag does not fully disable remote control

[hacetin]

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

1. Launch copilot --no-remote
2. Run /remote to check status
3. 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.

[copilot-cli-bot]

This appears to be resolved as of GitHub Copilot CLI v1.0.92. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.