Edgee CLI setup (recommended)
The fastest way to route Cursor through Edgee is the CLI. It authenticates, starts a local Edgee relay, and opens Cursor routed through it, no manual API key or base URL to configure.1
Install the Edgee CLI
- macOS / Linux
- Homebrew (macOS)
- Windows (PowerShell)
2
Launch Cursor through Edgee
Choose how you want to launch. Both options route requests through Edgee.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 Cursor routed through it. Token compression is enabled automatically.
- With aliases (recommended)
- Without aliases
Open Cursor (Edgee) from your app menu. The shortcut launches the editor through Edgee. See desktop shortcuts for supported platforms.
edgee alias cursor, then open Cursor (Edgee) like any other app. See the Edgee CLI page for details.
Manual setup (advanced)
Get your coding-agent key
Manual setup uses the key of your enrolled Cursor agent, not a standard API key created for LLM Router applications.- Open the Edgee Console and select your organization.
- In the header, click Set up coding agent or +, select Cursor, and click Enroll. If your agent is already enrolled, use its existing icon.
- Click the agent’s icon, then Advanced settings → Advanced.
- Under Edgee API key (for manual setup), click Reveal key, then the copy icon.
<YOUR_CODING_AGENT_KEY>.
Configure Cursor
You can also point Cursor at Edgee directly through its settings.1
Open Cursor Settings
In Cursor, go to Settings → Cursor Settings → Models.
2
Configure your API key
Scroll down to the API Keys section and do the following:
- Enable OpenAI API Key
- Paste the Cursor coding-agent key copied above
- Enable Override OpenAI Base URL
- Set the base URL to:
Use the key from your enrolled Cursor agent, retrieved in the steps above.
3
Add a model
Scroll up to Add or search model and enter any model from the Edgee model list.Click Add, then toggle it on.
Token compression is only available when routing through Edgee. You can use your own provider keys via BYOK — compression still applies as long as requests go through Edgee.
Next Steps
- Browse the model list to see all available models
- Set up observability to monitor usage and costs
- Explore retry and fallback for resilient routing