Remote environment hosting blocked by remote-control policy on personal Copilot Free account #5283

Describe the bug

On a personal GitHub account with Copilot Free and no organization membership, enabling Copilot CLI remote access fails even though local incoming-connection settings show as enabled. The environment status reports:

Request host.start failed with message: GitHub environment hosting is disabled by remote-control policy

The personal Copilot settings page shows Copilot CLI as Enabled. There is no organization policy available to inspect or change for this account. Please clarify whether remote control is supported for personal Copilot Free accounts and, if so, why environment hosting is blocked by policy.

Affected version

GitHub Copilot CLI 1.0.105 (Windows, installed with WinGet)

Steps to reproduce the behavior

1. Sign in to Copilot CLI with a personal GitHub account on the Copilot Free plan; the account is not a member of any organization.
2. Start an interactive CLI session and run /remote on.
3. Open /environments and view the Incoming connections tab.
4. Observe that Accept remote connections and Allow creating new sessions are On, but Remote access reports Error with Request host.start failed with message: GitHub environment hosting is disabled by remote-control policy.

Expected behavior

Please clarify the eligibility and policy requirements for remote control on a personal Copilot Free account. If it is supported, the CLI should be able to start remote environment hosting when the local incoming-connection settings are enabled, or report the specific account/policy setting that must be changed.

Additional context

The GitHub Copilot features page for this personal account shows GitHub Copilot Free, Copilot CLI: Enabled, and You do not belong to any organizations. The CLI was updated from 1.0.104 to 1.0.105; the error persists. The local user setting remoteSessions: true is enabled. A screenshot of the CLI Environments > Incoming connections status is attached.