Remote session disabled: could not resolve repository when using /remote on an organization repo #2751

Describe the bug

When running the /remote command in Copilot CLI v1.0.28 inside a repository owned by a GitHub organization, the following error is shown:

Remote session disabled: could not resolve repository

Affected version

v1.0.28 (copilot CLI)

Steps to reproduce the behavior

1. Login with /login using a GitHub user account that is a confirmed member of the organization.
2. Use a local clone of a repository owned by the organization.
3. Run the /remote command.
4. The error appears: Remote session disabled: could not resolve repository.

Expected behavior

The /remote session should start successfully, since:

• The repository exists under the organization.
• The logged-in user is a valid organization member.
• The org admin has enabled remote access for the user (without this, /remote cannot be invoked at all).

Additional context

• Re-logging in with /login does not help.
• The org admin confirmed remote access is enabled.
• It appears Copilot CLI may be attempting to resolve the repo under the logged-in user's personal account, instead of the organization.
• This is similar to gh copilot resolves wrong repository owner - uses local username instead of git remote #1328 (wrong repo owner resolution), but here the error is blocking /remote usage rather than failing MCP commands after connection.
• OS: windows 11
• Terminal: power shell