mirror of
https://github.com/coder/coder.git
synced 2026-09-24 15:04:27 +08:00
docs: mention AI Governance add-on (#21592)
Ironically, no AI was used to make this PR. --------- Co-authored-by: Matt Vollmer <matthewjvollmer@outlook.com>
This commit is contained in:
Ben Potter
co-authored by
Matt Vollmer
Matt Vollmer
parent
09f50046cb
commit
6346eb7af8
@@ -0,0 +1,59 @@
|
||||
# AI Governance Add-On (Premium)
|
||||
|
||||
Coder Workspaces already lets teams run AI tools like [Cursor](https://registry.coder.com/modules/coder/cursor) and [Claude Code](https://registry.coder.com/modules/coder/claude-code) inside their development environments. As adoption grows, many enterprises also need observability, management, and policy controls to support secure and auditable AI rollouts.
|
||||
|
||||
Coder’s AI Governance Add-On for Premium licenses includes a set of features that help organizations safely roll out AI tooling at scale:
|
||||
|
||||
- [AI Bridge](./ai-bridge/index.md): LLM gateway to audit AI sessions, central MCP server management, and policy enforcement
|
||||
- [Boundaries](./boundary/agent-boundary.md): Process-level firewalls for agents, restricting which domains can be accessed by AI agents
|
||||
- [Additional Tasks Use (via Agent Workspace Builds)](#how-coder-tasks-usage-is-measured): Additional allowance of Agent Workspace Builds for continued use of Coder Tasks.
|
||||
|
||||
## GA status and availability
|
||||
|
||||
Starting with Coder v2.30 (February 2026), AI Bridge and Agent Boundaries are generally available as part of the AI Governance Add-On.
|
||||
|
||||
If you’ve been experimenting with these features in earlier releases, you’ll see a notification banner in your deployment in v2.30. This banner is a reminder that these features have moved out of beta and are now included with the AI Governance Add-On.
|
||||
|
||||
In v2.30, this notification is informational only. A future Coder release will require the add-on to continue using AI Bridge and Agent Boundaries.
|
||||
|
||||
To learn more about enabling the AI Governance Add-On, pricing, or trial options, reach out to your [Coder account team](https://coder.com/contact/sales).
|
||||
|
||||
## Who should use the AI Governance Add-On
|
||||
|
||||
The AI Governance Add-On is for teams that want to extend that platform to support AI-powered IDEs and coding agents in a controlled, observable way.
|
||||
|
||||
It’s a good fit if you’re:
|
||||
|
||||
- Rolling out AI-powered IDEs like Cursor and AI coding agents like Claude Code across teams
|
||||
- Looking to centrally observe, audit, and govern AI activity in Coder Workspaces
|
||||
- Managing AI workflows against sensitive or regulated codebases
|
||||
- Expanding the use of Coder Tasks for AI-driven background work
|
||||
|
||||
If you already use other AI governance tools, such as third-party LLM gateways or vendor-managed policies, you can continue using them. Coder Workspaces can still serve as the backend for development environments and AI workflows, with or without the AI Governance Add-On.
|
||||
|
||||
## How Coder Tasks usage is measured
|
||||
|
||||
The usage metric used to measure Coder Tasks consumption is called **Agent Workspace Builds.**
|
||||
|
||||
An Agent Workspace Build is counted each time a workspace is started specifically for a coding agent to independently work on a Coder Task. Most of the work in this workspace is performed by the agent, not a human developer. Each Coder Task starts its own workspace, and the usage meter counts one Agent Workspace Build.
|
||||
|
||||
Traditional Coder Workspaces started manually by developers or scheduled to auto-start do not count as an Agent Workspace Build. These are considered daily-driver development environments where developers co-exist with their IDEs and coding assistants.
|
||||
|
||||
### Scenarios
|
||||
|
||||
| Scenario | Consumes Agent Workspace Build |
|
||||
|---------------------------------------------------------------------------------------------------|--------------------------------|
|
||||
| Developer creates a Coder Task to write end-to-end tests | Yes |
|
||||
| Automated pipeline creates a task via Coder Tasks CLI (with Claude Code) to review a pull request | Yes |
|
||||
| Developer resumes an old Coder Task order to continue prototyping | Yes |
|
||||
| Developer starts a workspace for use with VS Code and Jupyter | No |
|
||||
| Developer creates a workspace for use with Cursor and Claude Code CLI | No |
|
||||
| Developer creates a workspace for use with Coder AI Bridge and Boundaries | No |
|
||||
|
||||
In the future, additional capabilities for managing agents (beyond Coder Tasks) may also consume agent workspace builds.
|
||||
|
||||
### Agent Workspace Build Limits
|
||||
|
||||
Without proper controls and sandboxing, it is not recommended to open up Coder Tasks to a large audience in the enterprise. Coder Premium deployments include 1,000 Agent Workspace Builds, primarily for proof-of-concept use and basic workflows.
|
||||
|
||||
Our [AI Governance Add-On](./ai-governance.md) includes a shared usage pool of Agent Workspace Builds for automated workflows, along with limits that scale proportionately with user count. If you are approaching your deployment-wide limits, [contact us](https://coder.com/contact) to discuss your use case with our team.
|
||||
@@ -7,7 +7,7 @@ Coder Tasks is an interface for running & managing coding agents such as Claude
|
||||
Coder Tasks is best for cases where the IDE is secondary, such as prototyping or running long-running background jobs. However, tasks run inside full workspaces so developers can [connect via an IDE](../user-guides/workspace-access) to take a task to completion.
|
||||
|
||||
> [!NOTE]
|
||||
> Coder Tasks is free and open source. If you are a Coder Premium customer or want to run hundreds of tasks in the background, [contact us](https://coder.com/contact) for roadmap information and volume pricing.
|
||||
> Premium Coder deployments are limited to running 1,000 tasks. [Contact us](https://coder.com/contact) for pricing options or learn more about our [AI Governance Add-On](./ai-governance.md) to evaluate all of Coder's AI features.
|
||||
|
||||
## Supported Agents (and Models)
|
||||
|
||||
|
||||
+66
-65
@@ -986,76 +986,77 @@
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"title": "AI Governance",
|
||||
"description": "Features around managing agents at scale",
|
||||
"path": "./ai-coder/ai-governance.md",
|
||||
"state": ["premium"],
|
||||
"children": [
|
||||
{
|
||||
"title": "Agent Boundaries",
|
||||
"description": "Understanding Agent Boundaries in Coder Tasks",
|
||||
"path": "./ai-coder/boundary/agent-boundary.md",
|
||||
"state": ["beta"],
|
||||
"children": [
|
||||
{
|
||||
"title": "nsjail",
|
||||
"description": "Documentation for Namespace Jail",
|
||||
"path": "./ai-coder/boundary/nsjail.md"
|
||||
},
|
||||
{
|
||||
"title": "landjail",
|
||||
"description": "Documentation for LandJail",
|
||||
"path": "./ai-coder/boundary/landjail.md"
|
||||
},
|
||||
{
|
||||
"title": "Rules Engine",
|
||||
"description": "Documentation for the Boundary rules engine",
|
||||
"path": "./ai-coder/boundary/rules-engine.md"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"title": "AI Bridge",
|
||||
"description": "AI Gateway for Enterprise Governance \u0026 Observability",
|
||||
"path": "./ai-coder/ai-bridge/index.md",
|
||||
"icon_path": "./images/icons/api.svg",
|
||||
"state": ["premium", "beta"],
|
||||
"children": [
|
||||
{
|
||||
"title": "Setup",
|
||||
"description": "How to set up and configure AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/setup.md"
|
||||
},
|
||||
{
|
||||
"title": "Client Configuration",
|
||||
"description": "How to configure your AI coding tools to use AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/client-config.md"
|
||||
},
|
||||
{
|
||||
"title": "MCP Tools Injection",
|
||||
"description": "How to configure MCP servers for tools injection through AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/mcp.md",
|
||||
"state": ["early access"]
|
||||
},
|
||||
{
|
||||
"title": "Monitoring",
|
||||
"description": "How to monitor AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/monitoring.md"
|
||||
},
|
||||
{
|
||||
"title": "Reference",
|
||||
"description": "Technical reference for AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/reference.md"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"title": "MCP Server",
|
||||
"description": "Connect to agents Coder with a MCP server",
|
||||
"path": "./ai-coder/mcp-server.md",
|
||||
"state": ["beta"]
|
||||
},
|
||||
{
|
||||
"title": "Agent Boundaries",
|
||||
"description": "Understanding Agent Boundaries in Coder Tasks",
|
||||
"path": "./ai-coder/boundary/agent-boundary.md",
|
||||
"state": ["beta"],
|
||||
"children": [
|
||||
{
|
||||
"title": "nsjail",
|
||||
"description": "Documentation for Namespace Jail",
|
||||
"path": "./ai-coder/boundary/nsjail.md"
|
||||
},
|
||||
{
|
||||
"title": "landjail",
|
||||
"description": "Documentation for LandJail",
|
||||
"path": "./ai-coder/boundary/landjail.md"
|
||||
},
|
||||
{
|
||||
"title": "Rules Engine",
|
||||
"description": "Documentation for the Boundary rules engine",
|
||||
"path": "./ai-coder/boundary/rules-engine.md"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"title": "AI Bridge",
|
||||
"description": "AI Gateway for Enterprise Governance \u0026 Observability",
|
||||
"path": "./ai-coder/ai-bridge/index.md",
|
||||
"icon_path": "./images/icons/api.svg",
|
||||
"state": ["premium", "beta"],
|
||||
"children": [
|
||||
{
|
||||
"title": "Setup",
|
||||
"description": "How to set up and configure AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/setup.md"
|
||||
},
|
||||
{
|
||||
"title": "Client Configuration",
|
||||
"description": "How to configure your AI coding tools to use AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/client-config.md"
|
||||
},
|
||||
{
|
||||
"title": "MCP Tools Injection",
|
||||
"description": "How to configure MCP servers for tools injection through AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/mcp.md",
|
||||
"state": ["early access"]
|
||||
},
|
||||
{
|
||||
"title": "Monitoring",
|
||||
"description": "How to monitor AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/monitoring.md"
|
||||
},
|
||||
{
|
||||
"title": "Reference",
|
||||
"description": "Technical reference for AI Bridge",
|
||||
"path": "./ai-coder/ai-bridge/reference.md"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"title": "Tasks CLI",
|
||||
"description": "Coder CLI for managing tasks programmatically",
|
||||
"path": "./ai-coder/cli.md",
|
||||
"icon_path": "./images/icons/api.svg",
|
||||
"state": ["beta"]
|
||||
}
|
||||
]
|
||||
},
|
||||
|
||||
Reference in New Issue
Block a user