Client Configuration
Note
AI Gateway requires the AI Governance Add-On. As of Coder v2.32, deployments without the add-on will not be able to access AI Gateway.
Once AI Gateway is setup on your deployment, the AI coding tools used by your users will need to be configured to route requests via AI Gateway.
There are two ways to connect AI tools to AI Gateway:
- Base URL configuration (Recommended): Most AI tools allow customizing the base URL for API requests. This is the preferred approach when supported.
- AI Gateway Proxy: For tools that don't support base URL configuration, AI Gateway Proxy can intercept traffic and forward it to AI Gateway.
Note
AI Gateway works with tools running inside or outside of Coder workspaces. For non-workspace setup, visit External and Desktop Clients.
Base URLs
Most AI coding tools allow the "base URL" to be customized. In other words, when a request is made to OpenAI's API from your coding tool, the API endpoint such as /v1/chat/completions will be appended to the configured base. Therefore, instead of the default base URL of https://api.openai.com/v1, you'll need to set it to https://coder.example.com/api/v2/aibridge/openai/v1.
The exact configuration method varies by client — some use environment variables, others use configuration files or UI settings:
- OpenAI-compatible clients: Set the base URL (commonly via the
OPENAI_BASE_URLenvironment variable) tohttps://coder.example.com/api/v2/aibridge/openai/v1 - Anthropic-compatible clients: Set the base URL (commonly via the
ANTHROPIC_BASE_URLenvironment variable) tohttps://coder.example.com/api/v2/aibridge/anthropic
Replace coder.example.com with your actual Coder deployment URL.
Authentication
For information about authenticating with AI Gateway, visit AI Gateway Authentication.
Compatibility
The table below shows tested AI clients and their compatibility with AI Gateway.
| Client | OpenAI | Anthropic | BYOK | Notes |
|---|---|---|---|---|
| Coder Agents | ✅ | ✅ | ❌ | First-class AI Gateway client. Uses the Coder Agents provider config. |
| Mux | ✅ | ✅ | - | |
| Claude Code | - | ✅ | ✅ | |
| Codex CLI | ✅ | - | ✅ | |
| OpenCode | ✅ | ✅ | ✅ | |
| Factory | ✅ | ✅ | ✅ | |
| Cline | ✅ | ✅ | ✅ | |
| Kilo Code | ✅ | ✅ | ❌ | |
| VS Code | ✅ | ❌ | ❌ | Only supports Custom Base URL for OpenAI. |
| JetBrains IDEs | ✅ | ❌ | ❌ | Works in Chat mode via third-party model configuration. |
| Zed | ✅ | ✅ | ❌ | |
| GitHub Copilot | ⚙️ | - | - | Requires AI Gateway Proxy. Uses per-user GitHub tokens. |
| WindSurf | ❌ | ❌ | ❌ | No option to override base URL. |
| Cursor | ❌ | ❌ | ❌ | Override for OpenAI broken (upstream issue). |
| Sourcegraph Amp | ❌ | ❌ | ❌ | No option to override base URL. |
| Kiro | ❌ | ❌ | ❌ | No option to override base URL. |
| Gemini CLI | ❌ | ❌ | ❌ | No Gemini API support. Upvote this issue. |
| Antigravity | ❌ | ❌ | ❌ | No option to override base URL. |
Legend: ✅ supported, ⚙️ requires AI Gateway Proxy, ❌ not supported, - not applicable.
Configuring In-Workspace Tools
AI coding tools running inside a Coder workspace, such as IDE extensions, can be configured to use AI Gateway.
This section applies when you want template admins to preconfigure tools inside Coder workspaces. For tools running outside of a workspace, see External and Desktop Clients.
While users can manually configure these tools with a long-lived API key, template admins can provide a more seamless experience by pre-configuring them. Admins can automatically inject the user's session token with data.coder_workspace_owner.me.session_token and the AI Gateway base URL into the workspace environment.
In this example, Claude Code respects these environment variables and will route all requests via AI Gateway.
data "coder_workspace_owner" "me" {}
data "coder_workspace" "me" {}
resource "coder_agent" "dev" {
arch = "amd64"
os = "linux"
dir = local.repo_dir
env = {
ANTHROPIC_BASE_URL : "${data.coder_workspace.me.access_url}/api/v2/aibridge/anthropic",
ANTHROPIC_AUTH_TOKEN : data.coder_workspace_owner.me.session_token
}
... # other agent configuration
}
External and Desktop Clients
You can also configure AI tools running outside of a Coder workspace, such as local IDE extensions or desktop applications, to connect to AI Gateway. Use the same settings as the in-workspace case, configure the base URL and authenticate with a Coder API token.
For base URL setup, the client machine must have network access to the AI Gateway endpoint on your Coder deployment. Clients using AI Gateway Proxy must be able to reach the proxy endpoint and trust its CA certificate.
Users can generate a long-lived API token from the Coder UI or CLI. Follow the instructions at Sessions and API tokens to create one.
For headless scenarios, first create a service account, then generate a long-lived token for it.
Example
For clients supporting [base URL](#base-urls), eg. [Claude Code](./claude-code.md):export ANTHROPIC_BASE_URL="https://coder.example.com/api/v2/aibridge/anthropic"
export ANTHROPIC_AUTH_TOKEN="<your-coder-api-token>"
Replace coder.example.com with your Coder deployment URL.
For other clients setup AI Gateway Proxy. Configure the proxy endpoint and CA certificates:
export HTTPS_PROXY="https://coder:<your-coder-api-token>@<proxy-host>:8888"
export SSL_CERT_FILE="/path/to/coder-aibridge-proxy-ca.pem"
For proxy setup details, see AI Gateway Proxy setup.
For BYOK and workspace template examples, see full Claude Code example.
For complete setup instructions, see the supported client examples.