Skip to main content
GitHub Copilot in VS Code can run through Edgee for token compression and full observability over every session. The Edgee CLI starts a local relay and opens VS Code routed through it, no manual configuration.
1

Install the Edgee CLI

2

Launch VS Code Copilot through Edgee

Choose how you want to launch. Both options route requests through Edgee.
Open VS Code Copilot (Edgee) from your app menu. The shortcut launches the editor through Edgee. See desktop shortcuts for supported platforms.
If you are not signed in, Edgee starts sign-in automatically at launch. Follow the prompts and select your organization when asked.The CLI authenticates, starts a local Edgee relay, and opens VS Code routed through it. Token compression is enabled automatically.
VS Code must already be installed. Insiders builds are detected too.
After the session ends, the CLI prints a link to view token usage, compression savings, and cost breakdown in the Edgee Console.

​
Launch from your app menu

Install a desktop wrapper once, then open VS Code Copilot (Edgee) like any other app:
The wrapper appears in ~/Applications (macOS), your app menu (Linux), or the Start Menu (Windows). It is installed only when VS Code is present. See the Edgee CLI page for the full alias reference.

​
Next Steps

​
Verify the connection

Send one request from the configured client, then open Logs in the same Edgee organization. Check the served model, provider, and key. For a CLI-launched coding agent, also inspect its session report. If the request is missing, check that you launched through Edgee or saved the client’s gateway URL and coding-agent key. If it appears with an error, inspect the error before changing settings. See Troubleshooting and Gateway errors.