Skip to main content
Devin Desktop (Cognition’s June 2026 rebrand of the Windsurf editor) can run AI Reserve models — through the third-party agents it hosts, not through Devin itself. Its Agent Command Center runs ACP agents such as Codex CLI and Claude Code inside the editor. Each hosted agent reads its own configuration, so once you’ve connected it to AI Reserve it routes through the gateway exactly as it does standalone — every request metered and billed on your key. Devin’s own agents (cloud Devin, Devin Local, the Devin CLI) are the exception: they run exclusively on Cognition’s managed models. Cognition’s enterprise FAQ states Devin “does not currently support third-party LLM API keys”, and the app has no base-URL or key field — there is nothing to configure on Devin itself. The editor’s HTTP proxy setting doesn’t change that: it is corporate-network plumbing, and model traffic inside the tunnel still authenticates to Cognition — a gateway placed there never sees a request it could serve. Two steps:
  1. Connect the agent to AI Reserve — follow the Codex or Claude Code guide. Nothing here is Devin-specific (OpenCode is hosted too and works the same way).
  2. Add the agent in Devin Desktop — open the Agent Command Center and add Codex CLI or Claude Code, following Cognition’s ACP guide. ACP agents are available on Pro, Max, and Teams plans; Enterprise admins can ask their Cognition account team to enable them.
Mind the environment. Agents launched from Devin’s GUI may not inherit your shell profile. If you set Codex up by hand, its ~/.codex/config.toml persists but its env_key auth still reads AIRESERVE_API_KEY from the process environment — have Devin inject it per agent (the Agents tab, or devin.acp.agentEnv.<agent> in its settings), or GUI launches fail auth. The aireserve CLI sidesteps this: its Codex provider authenticates with a helper command rather than an environment variable, so GUI launches work as-is. Claude Code needs no extra step either way: the env block of ~/.claude/settings.json (the one-click connect page or the CLI writes it for you) persists everything the session needs.
Usage from these agents appears in your AI Reserve analytics as Codex or Claude Code — the requests genuinely come from those harnesses, so attribution is correct with no extra setup, unless the API key itself is tagged to a specific tool (a key’s category takes precedence over what the traffic looks like).