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

# Claude Desktop (Beta)

> Use Claude Code inside Claude Desktop through Edgee.

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

Edgee supports **Claude Code inside Claude Desktop**, with your existing Claude subscription. Regular Claude chat is outside this integration and does not appear in Edgee. 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

        # 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 Claude Desktop through Edgee">
    <Tabs>
      <Tab title="With aliases (recommended)">
        Open **Claude Desktop (Edgee)** from your app menu. See [desktop shortcuts](/docs/cli/aliases) for availability on your platform.
      </Tab>

      <Tab title="Without aliases">
        ```bash theme={"dark"}
        edgee launch claude-desktop
        ```
      </Tab>
    </Tabs>

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

Open Claude Code inside the app and run a coding task. On macOS, follow the first-launch prompt to trust the local relay certificate. Keep the launch process running while using the app.

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