Skip to content

Edgee Demo Day · November 10

Register
Agent Gateway
Coding assistants

GitHub Copilot CLI

Route GitHub Copilot CLI requests through Edgee using your Copilot subscription.

Use GitHub Copilot CLI through Edgee with your existing Copilot subscription.

Connect through Edgee

Install the Edgee CLI

curl -fsSL https://edgee.ai/install.sh | bash

Launch GitHub Copilot CLI through Edgee

edgee launch copilot-cli

To make the plain copilot command launch through Edgee, run edgee alias copilot-cli.

Edgee starts sign-in automatically if needed. Follow the prompts and select your organization when asked.

Run a coding task in the launched Copilot CLI. Keep the Edgee launch process running during the session.

What Edgee adds to the session

  • Statusline. The first launch adds Edgee's usage segment to Copilot CLI's statusline, unless you already configured your own. See Statusline.
  • Session metadata. When Edgee MCP is enabled, Copilot CLI gets the Edgee session tools under the edgee-session server and names the session on its first turn. See Enriching sessions with MCP tools.
  • Organization plugins. Plugins assigned to you load for this session only, with nothing written to ~/.copilot. See Plugins.

Verify the connection

Send a request, then open Logs in the same Edgee organization. Check its model, provider, and usage. Open Sessions to inspect the coding session.

If requests are missing, confirm you launched through Edgee and used the supported surface described above. For desktop apps, close any existing instance and relaunch through Edgee. See Troubleshooting.

Next steps