Skip to main content
The Edgee CLI is the fastest way to route your coding agent through Edgee. Instead of manually configuring environment variables and API keys, the CLI handles authentication, session tracking, and launching your agent in a single command.

Supported Tools

Claude Code

Anthropic’s official CLI for interactive coding with AI.

Codex

OpenAI’s CLI agent for software engineering tasks.

OpenCode

Open-source coding agent with multi-model support.

CodeBuddy

CLI coding agent, routed through Edgee.

Crush

Charm’s terminal coding agent, routed through Edgee.

Cursor

Cursor IDE, routed through a local Edgee relay.

GitHub Copilot (VS Code)

Copilot in VS Code, routed through a local Edgee relay.
CLI agents (Claude Code, Codex, OpenCode, CodeBuddy, Crush) run in your terminal. Cursor and VS Code Copilot are desktop editors: edgee launch starts a local Edgee relay and opens the editor routed through it.

Installation

Verify the installation:

Quick Start

Launch your coding agent
That’s it. Your coding agent is now running with Edgee compression and observability enabled. After your session ends, the CLI prints a link to view your session analytics in the Edgee Console.

Commands

Anthentication commands

edgee auth login

Authenticate with Edgee for a specific provider. Opens a browser window for OAuth-based login. Your API key and credentials are saved to ~/.config/edgee/credentials.toml. If you want to use multiple Edgee profiles, you can add --profile <profile-name> to this command to declare the profile you want to use.

edgee auth status

Display the current authentication status for all configured providers, including the logged-in email and connection mode.

edgee auth list

List all configured profiles. Yes, because you can have multiple Edgee profiles, using --profile <profile-name> when you log in.

edgee auth switch

Switch to a different profile.

Launch commands

Launch your coding agent.

edgee launch claude

Launch Claude Code with all Edgee configuration automatically injected. The CLI sets the required environment variables (ANTHROPIC_BASE_URL, authentication headers, session ID) and starts Claude Code.
You can pass any Claude Code arguments after the command:
If you haven’t authenticated yet, the CLI will prompt you to log in first. It will also ask you to select a connection mode on first launch:
  • Claude Pro/Max: uses your Anthropic subscription, Edgee compresses traffic to extend session duration
  • API Billing: uses Edgee API keys for direct billing, reducing token costs

edgee launch codex

Launch Codex with Edgee routing automatically configured. The CLI passes the required provider configuration to Codex and starts a new session.
You can pass any Codex arguments after the command:
Connection modes for Codex:
  • ChatGPT Plus/Pro: uses your OpenAI subscription with Edgee compression
  • API Billing: uses Edgee API keys for direct billing

edgee launch opencode

Launch OpenCode with Edgee routing automatically configured.

edgee launch codebuddy

Launch CodeBuddy with Edgee routing automatically configured.

edgee launch crush

Launch Charm’s Crush with Edgee routing automatically configured.

Apps & editors

Cursor and VS Code Copilot are desktop editors, not terminal CLIs. edgee launch authenticates, starts a local Edgee relay, and opens the editor routed through it, so its requests get compression and observability like any CLI agent.
Both require the target app to be installed. See the Cursor and GitHub Copilot integration pages for details.

Other commands

edgee stats

Show the stats of your latest sessions.

edgee alias

Install launch aliases so you can start each tool by its own name instead of typing edgee launch <tool> every time.
What it installs:
  • CLI agents (claude, codex, opencode, codebuddy, crush) — on macOS/Linux, PATH shims in ~/.edgee/bin; on Windows, shell aliases. Running claude then transparently runs edgee launch claude.
  • Desktop editors (cursor, copilot-vscode) — a desktop wrapper (macOS .app, Linux .desktop, Windows Start Menu shortcut) that opens the editor through Edgee. Installed only when the editor is already present; otherwise skipped with a note.
Scope it to one target, or undo:
After a fresh install on macOS/Linux, reopen your terminal (or run exec $SHELL -l) so ~/.edgee/bin lands on your PATH.

edgee reset

Reset your credentials and connection mode for a provider. Useful if you need to switch accounts, change your connection mode, or re-authenticate.

edgee self-update

Check for updates and install the latest version of the Edgee CLI.

Configuration

The CLI stores credentials in ~/.config/edgee/credentials.toml with restricted file permissions (600).
You don’t need to edit this file manually. The CLI manages it through edgee init, edgee auth login, and edgee reset.

Session Tracking

Every edgee launch session is assigned a unique session ID. When the agent exits, the CLI prints a link to a detailed report in the Edgee Console. See Sessions for the full breakdown.

How It Works

When you run edgee launch claude or edgee launch codex, the CLI:
  1. Verifies your authentication (prompts login if needed)
  2. Generates a unique session ID
  3. Configures the appropriate environment variables and headers
  4. Launches the coding agent as a child process with Edgee routing enabled
  5. Prints a session analytics URL when the session ends
All requests from your coding session flow through Edgee’s API, where token compression, cost tracking, and observability are applied automatically.

Next Steps