Live now · Get your API key

Coding agents

Bring Ambient's verified open models into the coding agent you already use, whether Claude Code, Codex, OpenCode, or OpenClaw. Keep your agent as the orchestrator and route the token-heavy work to the network, or run the whole session on Ambient.

Keep the coding agent you already use, and point it at Ambient for inference. You decide how much to hand over: keep your agent as the orchestrator and route only the token-heavy building to open models, or run the entire session on the network. One API key, verified inference, and you pick the model per task.

YOUR CODING AGENTAMBIENTOPEN MODELSClaude CodeCodexOpenCodeOpenClawAmbientone API keyverified inferenceyou pick the modelGLM 5.2Kimi K2.7 CodeDeepSeek V4 Flash…and more on the network

A three-column diagram. On the left, four coding agents (Claude Code, Codex, OpenCode, and OpenClaw) each connect to a central Ambient node. The Ambient node is labelled one API key, verified inference, and you pick the model. From Ambient, three arrows fan out to the open models the network serves: GLM 5.2, Kimi K2.7 Code, and DeepSeek V4 Flash, and more live on the network. The figure shows that whichever agent you use, it routes through a single Ambient integration to reach verified open models.

Every integration lands on the same surface: your agent talks to Ambient with one key, and Ambient serves the open models. You choose which one, and every response carries a verified-inference receipt.

Pick your integration#

Each agent connects a little differently. Start here, then follow the guide for your tool.

Agent How it connects Reach for it when
Claude Code The ambient-code plugin (Claude orchestrates, routes the bulk to Ambient), or point Claude Code's model at Ambient for the whole session You want a frontier model's judgment at open-model rates on the volume, or the whole session on Ambient
Codex The ambient-codex plugin, reached with $ambient; Delegate or Ambient-session (takeover) mode routes the bulk to Ambient You work in Codex and want audits, builds, and large-repo work routed to Ambient while Codex orchestrates
OpenCode Select Ambient from OpenCode's built-in provider menu Ambient is a first-class provider option already in your tool
OpenClaw Install the Ambient plugin from ClawHub You run OpenClaw and want Ambient as its inference provider

Two ways to work#

Across every integration, the same two working styles apply. Pick per project, or switch mid-session.

Your agent stays the designer and reviewer. When there is a lot of code to write, it hands the token-heavy generation to an open model on Ambient, then reads every file back before anything is integrated. A frontier model's judgment on each line, open-model rates for the volume.

Reach for this when the work is high-volume but well-specified (scaffolding, CRUD, test suites, mechanical refactors) and you want to spend premium tokens on the design and the review, not the typing.

A second opinion on every commit#

Whichever agent builds, have a different model on Ambient review the diff. Independent readers catch what the author misses, at a price where running it on every commit is affordable. Both the Claude Code and Codex plugins ship an audit command for exactly this.

What every integration shares#

  • One key. Create it once at app.ambient.xyz/keys; it works across every agent.
  • Your model choice. The model catalog shows what the network is serving right now.
  • Verified inference. Every response carries a receipt. See Verified inference for what it proves.
  • Zero data retention by default. You decide, per task, what leaves your machine and where it goes.