> ## 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 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

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

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

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

  <Step title="Launch GitHub Copilot CLI through Edgee">
    ```bash theme={"dark"}
    edgee launch copilot-cli
    ```

    `edgee alias` does not currently provide a shell alias for this target. Use the explicit launch command.

    Edgee starts sign-in automatically if needed. Follow the prompts and select your organization when asked.
  </Step>
</Steps>

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

## 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](/docs/troubleshooting).

## Next steps

* [Routing strategies](/docs/features/routing-strategies): apply your team’s routing policy.
* [Sessions](/docs/features/observability/sessions): inspect requests and usage.