WSL hosts (Preview): project check fails for GHE data-residency accounts — copilotd calls api.github.com (rpc error -32007)

[FBakkensen]

Short summary

WSL hosts (Preview): project check and folder browse fail for a GHE data-residency account because copilotd authenticates against api.github.com.

Affected version or release

GitHub Copilot app 1.1.16 (Windows); WSL daemon copilotd 0.7.3 (installed by the app)

Installation context

Windows desktop app signed in with a GitHub Enterprise Cloud data-residency account (https://<tenant>.ghe.com). WSL 2, Ubuntu, environment shows Connected on ws://127.0.0.1:<port>. git 2.43.0 is on the daemon's PATH.

What happened?

With the WSL environment connected, Add project for any valid git repository shows "Couldn't check this project path. Make sure the environment is connected, then try again." and the button stays disabled. Browse cannot list ~ and surfaces the underlying error:

git error on host `wsl:Ubuntu`: list_workspace_directory failed on remote host:
rpc error -32007: authentication required for https://api.github.com

It happens equally for a repository whose origin is on the GHE tenant and for a control repository whose origin is on github.com, so the repository remote is not the trigger. The daemon receives sealed auth for the GHE account (--require-sealed-auth) but targets api.github.com, where a GHE token is not valid.

Steps to reproduce

1. Sign in to the app with a GHE data-residency (*.ghe.com) account.
2. Settings → Environments → connect WSL: Ubuntu (status becomes Connected).
3. Projects on this host → Add project → enter the Linux path of a valid git repository.
4. Observe "Couldn't check this project path…".
5. Click Browse → "Couldn't load this folder" with the -32007 error above.

Expected behavior

Daemon API calls follow the signed-in account's host (https://<tenant>.ghe.com/api/v3), so folder listing and project validation succeed and a WSL-hosted session can be created.

Additional context

• The CLI server spawned by copilotd (copilot --server --stdio --no-auto-update --no-auto-login) logged only its startup lines and zero requests, so the failure is inside copilotd's git/GitHub layer before any git or CLI work.
• Logging into the Copilot CLI inside WSL (copilot login, github.com account) and clicking Reconnect does not change the result; the daemon uses the sealed app auth.
• The form's error text ("Make sure the environment is connected") is misleading here; the environment is connected and the port is listening. Surfacing the RPC error in the Add-project form would have saved time.
• Related: copilotd update --check-only reports 0.7.5 available, but copilotd update fails with unrecognised archive extension on copilotd.update.<pid>.archive. The release URL https://copilotd.blob.core.windows.net/release/v0.7.5/... returns 409 Public access is not permitted on this storage account, so the updater saved an error response as the archive.