You can use Copilot while editing a remote project through VS Code Remote SSH. Set up the SSH workspace first, then enable Copilot in that window and verify the actual extension and account state. Do not assume every Copilot component must be installed and signed in separately on both machines.
Prepare the SSH Workspace and Copilot Access
You need a supported local VS Code installation, Microsoft’s Remote – SSH extension, an SSH client and authorized access to a compatible remote host. Confirm that an ordinary SSH connection works before adding AI assistance. VS Code installs its server as part of opening the remote workspace; follow the Remote SSH setup guide for host requirements.
Use the GitHub account that has your Copilot access. A paid subscription is not universally required: eligible accounts can use Copilot Free within its limits. An employer-provided seat may impose feature and data-handling policies. Review whether sending the remote project’s content to Copilot is permitted before testing with work code.
SSH authentication and GitHub Copilot authentication are separate. The SSH key lets you reach the server; it does not provide a Copilot seat.
Enable Copilot in the Connected Window
- Run Remote-SSH: Connect to Host… and choose the intended host. Open the project folder and verify the SSH indicator.
- Open Extensions in that connected window. Enable or install the official Copilot components if needed, following VS Code’s offered installation location.
- Use the Copilot status menu’s Use AI Features action if setup is required, and complete the GitHub sign-in prompts.
- Confirm the active GitHub account. For multiple accounts, the Accounts menu offers Manage Extension Account Preferences; select GitHub Copilot Chat and the intended account where available.
- Try one small inline-completion task and one read-only chat question about a non-sensitive file. These verify different features; one succeeding does not prove the other is configured.
The current Copilot setup guide describes account selection. VS Code’s extension-host architecture allows local UI components and remote workspace components. Use the Extensions groups and activation details to see what is actually running instead of forcing remote.extensionKind overrides.
Troubleshoot SSH and Copilot Separately
If file access or the remote terminal fails, inspect the Remote – SSH output first. If the workspace is healthy but Copilot fails, inspect Copilot’s status and output channels. Read the tooltip or error rather than interpreting a warning icon as one specific cause.
For an account error, confirm the entitlement and selected account. Refresh authentication only if warranted; do not copy credentials into the remote filesystem. For a network error, identify whether the failed request originates locally or remotely and test that route.
GitHub documents HTTPS probes to https://copilot-proxy.githubusercontent.com/_ping and, for chat, https://api.githubcopilot.com/_ping. Reaching github.com or running ICMP ping does not test all Copilot services. There is no universal 100-millisecond threshold that diagnoses Copilot latency.
Apply only an administrator-approved proxy or firewall change. Keep certificate validation enabled. An SSH keepalive may help diagnose an idle SSH disconnect, but it does not reduce model-generation time or fix Copilot HTTPS authentication.
Verify the Result and Keep Remote Changes Reviewable
Repeat the same small test in the same remote folder after each change. Check the active account, feature availability, workspace policy and actual response. A successful sign-in or a particular icon shape is not enough.
For further investigation, use Chat Diagnostics and Copilot output logs as described in the VS Code troubleshooting guide. Include local and remote versions and a clear reproduction; remove secrets and proprietary content before sharing logs.
If you later use an editing agent, remember that it may change remote project files and execute commands with your remote user’s access. Work in a recoverable branch or copy, inspect diffs and test results, and keep production credentials and unrelated directories outside the task’s reach.
Official documentation checked: October 14, 2026.