Feature Request: /remote should support non-GitHub git repositories (e.g. GitLab, Bitbucket)

[herbeus]

Problem

/remote fails with Remote session disabled: not in a GitHub repository when used in a GitLab (or other) repository.

Proposed Solution

The remote session feature should work independently of the git host — session control via GitHub account, regardless of where the code is hosted.

Use Case

Teams using GitLab want to use /remote to control their Copilot CLI session from GitHub web/mobile, but are blocked by the repository host check.

Additional Context

The CLI is already authenticated via GitHub, so the restriction to GitHub-hosted repos feels unnecessary for the remote control functionality itself.

[kagudimov]

I ran into a similar issue. This is a workaround, suitable for cases where repository association isn't needed. The following steps worked for me:

1. /cwd ../test -- to leave the repository, so Copilot wouldn't try to associate it with a repository from a different account.
2. /remote on
3. /cwd ../myrepo -- to go back into the working repository.

[copilot-cli-bot]

This appears to be resolved as of GitHub Copilot CLI v1.0.86. 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.