Skip to main content
CodeBuddy is a CLI coding agent. Route it through Edgee to reduce token costs with lossless compression and gain full observability over every session. The fastest way to connect CodeBuddy to Edgee is the CLI, no environment variables to set by hand.
1

Install the Edgee CLI

2

Launch CodeBuddy through Edgee

Choose how you want to launch. Both options route requests through Edgee.
With aliases installed in the previous step, use your usual command:
The alias runs edgee launch for you, so requests go 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, configures routing, and starts CodeBuddy, all in one command. Token compression is enabled automatically.
CodeBuddy must already be installed. See the CodeBuddy repository for install instructions.
After the session ends, the CLI prints a link to view token usage, compression savings, and cost breakdown in the Edgee Console.

​
Manual setup (advanced)

​
Get your coding-agent key

Manual setup uses the key of your enrolled CodeBuddy agent, not a standard API key created for LLM Router applications.
  1. Open the Edgee Console and select your organization.
  2. In the header, click Set up coding agent or +, select CodeBuddy, and click Enroll. If your agent is already enrolled, use its existing icon.
  3. Click the agent’s icon, then Advanced settings → Advanced.
  4. Under Edgee API key (for manual setup), click Reveal key, then the copy icon.
Use this key wherever the configuration below shows <YOUR_CODING_AGENT_KEY>.

​
Configure CodeBuddy

CodeBuddy reads its endpoint and headers from environment variables. Set the following in your shell configuration (~/.bashrc, ~/.zshrc, etc.):
Replace <YOUR_CODING_AGENT_KEY> with the coding-agent key copied above.

​
Next Steps

​
Verify the connection

Send one request from the configured client, then open Logs in the same Edgee organization. Check the served model, provider, and key. For a CLI-launched coding agent, also inspect its session report. If the request is missing, check that you launched through Edgee or saved the client’s gateway URL and coding-agent key. If it appears with an error, inspect the error before changing settings. See Troubleshooting and Gateway errors.