You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ai-coder/ai-bridge/client-config.md
+41-26Lines changed: 41 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,30 @@ Again, the exact environment variable or setting naming may differ from tool to
24
24
25
25
##Configuring In-Workspace Tools
26
26
27
-
Template admins can pre-configure workspaces to route all AI tool requests through AI Bridge, providing a seamless and secure experience for users. This can be done for both Coder Tasks and other AI tools running in the workspace.
27
+
AI coding tools running inside a Coder workspace, such as IDE extensions, can be configured to use AI Bridge.
28
+
29
+
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 Bridge base URL into the workspace environment.
30
+
31
+
In this example, Claude code respects these environment variables and will route all requests via AI Bridge.
32
+
33
+
This is the fastest way to bring existing agents like Roo Code, Cursor, or Claude Code into compliance without adopting Coder Tasks.
AI coding tools running inside a Coder workspace, such as IDE extensions, can be configured to use AI Bridge.
65
-
66
-
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. Similar to the Coder Tasks example, admins can use Terraform data sources like`data.coder_workspace_owner.me.session_token` to automatically inject the user's session token and the AI Bridge base URL into the workspace environment.
67
-
68
-
This is the fastest way to bring existing agents like Roo Code, Cursor, or Claude Code into compliance without adopting Coder Tasks.
69
-
70
85
##External and Desktop Clients
71
86
72
87
You can also configure AI tools running outside of a Coder workspace, such as local IDE extensions or desktop applications, to connect to AI Bridge.
@@ -79,23 +94,23 @@ Users can generate a long-lived API key from the Coder UI or CLI. Follow the ins
79
94
80
95
The table below shows tested AI clients and their compatibility with AI Bridge. Click each client name for vendor-specific configuration instructions. Report issues or share compatibility updates in the[aibridge](https://github.com/coder/aibridge) issue tracker.
|[Claude Code](https://docs.claude.com/en/docs/claude-code/settings#environment-variables)| N/A| ✅| Works out of the box and can be preconfigured in templates.|
85
-
| Claude Code (VS Code)| N/A| ✅| May require signing in once; afterwards respects workspace environment variables.|
86
-
|[Cursor](https://cursor.com/docs/settings/api-keys)| ⚠️| ❌| Only non-reasoning models like`gpt-4.1` are available when using a custom endpoint. Requests still transit Cursor's cloud. There is no central admin setting to configure this.|
87
-
|[Roo Code](https://docs.roocode.com/features/api-configuration-profiles#creating-and-managing-profiles)| ✅| ✅| Use the**OpenAI Compatible** provider with the legacy format to avoid`/v1/responses`.|
88
-
|[Codex CLI](https://github.com/openai/codex/blob/main/docs/config.md#model_providers)| ✅| N/A|`gpt-5-codex` support is[in progress](https://github.com/coder/aibridge/issues/16).|
89
-
|[GitHub Copilot (VS Code)](https://docs.github.com/en/copilot/configuring-github-copilot/configuring-network-settings-for-github-copilot)| ✅| ❌| Requires the pre-release extension. Anthropic endpoints are not supported.|
90
-
| Goose| ❓| ❓||
91
-
| Goose Desktop| ❓| ✅||
92
-
| WindSurf| ❌| —| No option to override the base URL.|
93
-
| Sourcegraph Amp| ❌| —| No option to override the base URL.|
94
-
| Kiro| ❌| —| No option to override the base URL.|
95
-
|[Copilot CLI](https://github.com/github/copilot-cli/issues/104)| ❌| ❌| No support for custom base URLs and uses a`GITHUB_TOKEN` for authentication.|
96
-
|[Kilo Code](https://kilocode.ai/docs/features/api-configuration-profiles#creating-and-managing-profiles)| ✅| ✅| Similar to Roo Code.|
97
-
| Gemini CLI| ❌| ❌| Not supported yet (`GOOGLE_GEMINI_BASE_URL`).|
98
-
|[Amazon Q CLI](https://aws.amazon.com/q/)| ❌| ❌| Limited to Amazon Q subscriptions; no custom endpoint support.|
|[Claude Code](https://docs.claude.com/en/docs/claude-code/settings#environment-variables)| N/A| ✅| Works out of the box and can be preconfigured in templates.|
100
+
| Claude Code (VS Code)| N/A| ✅| May require signing in once; afterwards respects workspace environment variables.|
101
+
|[Cursor](https://cursor.com/docs/settings/api-keys)| ⚠️| ❌| Only non-reasoning models like`gpt-4.1` are available when using a custom endpoint. Requests still transit Cursor's cloud. There is no central admin setting to configure this.|
102
+
|[Roo Code](https://docs.roocode.com/features/api-configuration-profiles#creating-and-managing-profiles)| ✅| ✅| Use the**OpenAI Compatible** provider with the legacy format to avoid`/v1/responses`.|
103
+
|[Codex CLI](https://github.com/openai/codex/blob/main/docs/config.md#model_providers)| ✅| N/A|`gpt-5-codex` support is[in progress](https://github.com/coder/aibridge/issues/16).|
104
+
|[GitHub Copilot (VS Code)](https://code.visualstudio.com/docs/copilot/customization/language-models#_use-an-openaicompatible-model)| ✅| ❌| Requires the pre-release extension. Anthropic endpoints are not supported.|
Copy file name to clipboardExpand all lines: docs/ai-coder/ai-bridge/mcp.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,4 +63,4 @@ If you have the `oauth2` and `mcp-server-http` experiments enabled, Coder's own
63
63
64
64
- **Coder MCP tools not being injected**: in order for Coder MCP tools to be injected, the internal MCP server needs to be active. Follow the instructions in the [MCP Server](../mcp-server.md) page to enable it.
65
65
66
-
- **External Auth tools not being injected**: this is generally due to the requesting user not being authenticated against the External Auth app; when this is the case, no attempt is made to connect to the MCP server.
66
+
- **External Auth tools not being injected**: this is generally due to the requesting user not being authenticated against the[External Auth](../../admin/external-auth/index.md) app; when this is the case, no attempt is made to connect to the MCP server.