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

# Codex Desktop (Beta)

> Use the Codex tab in the ChatGPT desktop app through Edgee.

<Note>
  **Beta:** this integration is available for testing and may have limitations.
</Note>

Edgee supports the **Codex tab in the ChatGPT desktop app**, with your existing subscription for Codex. The regular ChatGPT tab is outside this integration. The app launch target supports macOS and Windows.

## 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 Codex Desktop through Edgee">
    ```bash theme={"dark"}
    edgee launch codex-desktop
    ```

    `edgee alias` does not currently provide an app shortcut 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>

Open the Codex tab and run a coding task. Keep the launch terminal open until you quit the app: Edgee temporarily configures its provider and restores the configuration when the app exits.

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