> ## Documentation Index
> Fetch the complete documentation index at: https://www.edgee.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub Copilot (VS Code)

> Route GitHub Copilot in VS Code through Edgee to cut token costs and gain full observability, with one command.

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.

## Edgee CLI setup (recommended)

<Steps>
  <Step title="Install the Edgee CLI">
    <Tabs>
      <Tab title="macOS / Linux">
        ```bash theme={"dark"}
        curl -fsSL https://edgee.ai/install.sh | bash

        # Accept the alias prompt (recommended).
        # If skipped: edgee alias
        # Reopen your terminal afterward.
        ```
      </Tab>

      <Tab title="Homebrew (macOS)">
        ```bash theme={"dark"}
        brew install edgee-ai/tap/edgee

        # Enable aliases (recommended).
        edgee alias
        # Reopen your terminal afterward.
        ```
      </Tab>

      <Tab title="Windows (PowerShell)">
        ```powershell theme={"dark"}
        irm https://edgee.ai/install.ps1 | iex

        # Enable aliases (recommended).
        edgee alias
        # Reopen your terminal afterward.
        ```
      </Tab>
    </Tabs>
  </Step>

  <Step title="Launch VS Code Copilot through Edgee">
    Choose how you want to launch. Both options route requests through Edgee.

    <Tabs>
      <Tab title="With aliases (recommended)">
        Open **VS Code Copilot (Edgee)** from your app menu. The shortcut launches the editor through Edgee. See [desktop shortcuts](/docs/cli/aliases) for supported platforms.
      </Tab>

      <Tab title="Without aliases">
        Launch explicitly through Edgee each time:

        ```bash theme={"dark"}
        edgee launch copilot-vscode
        ```

        No alias setup is required.
      </Tab>
    </Tabs>

    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.

    <Note>
      VS Code must already be installed. Insiders builds are detected too.
    </Note>
  </Step>
</Steps>

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:

```bash theme={"dark"}
edgee alias copilot-vscode
```

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](/docs/features/cli) page for the full alias reference.

## Next Steps

* Learn more about the [Edgee CLI](/docs/features/cli) and its launch commands
* Set up [observability](/docs/features/observability) to monitor usage and costs
* Explore [retry and fallback](/docs/features/retry-and-fallback) for resilient routing

## 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](/docs/troubleshooting) and [Gateway errors](/docs/llm-router/api-reference/errors).