Skip to main content
Kimi Code is Moonshot AI’s terminal 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 Kimi Code to Edgee is the CLI. It authenticates, points Kimi Code at the gateway for the duration of the session, and starts it, no config file to edit by hand.
1

Install the Edgee CLI

2

Launch Kimi Code 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 Kimi Code, all in one command. Token compression is enabled automatically.
Kimi Code must already be installed. See the Kimi Code documentation for install instructions, or run curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash.
You can pass any Kimi Code arguments after the command:
After the session ends, the CLI prints a link to view token usage, compression savings, and cost breakdown in the Edgee Console.

​
What the session runs on

Kimi Code launched through Edgee runs on Edgee credentials and the Edgee model catalog, not on a Moonshot subscription. The CLI provisions a Kimi Code key against your Edgee organization on first launch; a Moonshot plan is not required and is not used. The provider Edgee configures lives in memory for the length of the session. Nothing is written to ~/.kimi-code/config.toml, and running kimi on its own afterwards is unaffected.

​
Model selection

The session is pinned to moonshotai/kimi-k2.7-code. That is a starting point, not a restriction: Edgee’s routing engine decides which provider and model actually serve each request, so routing strategies and retry and fallback apply as they do for any other agent. To pin a different catalog model instead, set EDGEE_KIMI_MODEL before launching:

​
Compression settings

Compression, fallback, and rerouting for the Kimi Code key are managed like any other agent:
See token compression for what each setting does.

​
Manual setup (advanced)

​
Get your coding-agent key

Manual setup uses the key of your enrolled Kimi Code 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 Kimi Code, 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 Kimi Code

Prefer to configure Kimi Code yourself? Kimi Code does not read provider credentials from the usual environment variables — api_key and base_url come from config.toml. The one channel that does read the shell is the KIMI_MODEL_* family, which synthesizes a provider and a model alias in memory:
Replace <YOUR_CODING_AGENT_KEY> with the coding-agent key copied above.
Three details worth knowing:
  • KIMI_MODEL_NAME is both the model id and the switch. Unset, none of the other variables are read. Set with a required one missing, Kimi Code fails at startup rather than quietly calling Moonshot.
  • KIMI_MODEL_BASE_URL carries no /v1 suffix. With KIMI_MODEL_PROVIDER_TYPE=anthropic, the SDK appends /v1/messages itself, the same way ANTHROPIC_BASE_URL works for Claude Code.
  • KIMI_CODE_CUSTOM_HEADERS takes one Name: Value per line and is what groups requests into a session in the Console. Without x-edgee-session-id, requests are still routed and metered, but they do not group into one session.
edgee launch kimi sets all of these for you, including a fresh session id and your repository origin, and adds nothing to your shell configuration.

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