v1.0.51 Remote sessions are not enabled. Contact your organization administrator to enable remote sessions.

[aarondglover]

Describe the bug

After updating to Copilot v1.0.51, Copilot displays the following warning when I attempt to run /remote on after startup:

Remote sessions are not enabled. Contact your organization administrator to enable remote sessions.

As far as I can tell, I am not explicitly requesting remote mode, and I cannot find any GitHub organisation policy or personal account setting that would explain this restriction.

This appears consistent with the v1.0.51 changelog item:

Only show remote session startup failure when remote mode is explicitly requested via --remote or enabled in user configuration

However I can not find said policy/setting in the Github UI.

Maybe this isn't a bug with the product but rather with the Github Settings/Policies UI

Affected version

GitHub Copilot CLI 1.0.51

Steps to reproduce the behavior

• Update Copilot to v1.0.51.
• Start Copilot normally, without explicitly passing --remote. (with, or without --experimental)
• run /remote on
• observe output

Expected behavior

remote should be enabled

Additional context

No response

[patrikhellgren]

I am also seeing this.
I am an administrator for our organization and have checked that the Remote Control policy in the organization settings is enabled.
I am running this inside of a non-github repo if that could be an issue.
It works when starting the CLI session with copilot --remote.

[micronwave]

I am also getting this response. Personal account, no org, re-authed and still getting "Remote sessions are not enabled. Contact your organization administrator to enable remote sessions."

[melodiouscode]

Same problem, have tried toggling on and off in org settings, and a reinstall of the cli. No luck. Running with copilot --remote works.

[patrikhellgren]

This works for me in version 1.0.54 so it seems fixed.