mirror of
https://github.com/coder/coder.git
synced 2026-09-22 05:05:20 +08:00
## Summary AI Governance is now included with Premium licenses instead of being sold as a separate per-user add-on. This updates `docs/` to describe the new packaging, removes "Add-On" from AI Governance references, and refreshes the editions architecture diagram. ## Changes - **`docs/ai-coder/ai-governance.md`**: title is now "AI Governance"; rewrote the licensing statements (previously "a separate, per-user license... not included with a Premium subscription and must be purchased separately") to state it is included with Premium. The usage-pool section now attributes the shared Agent Workspace Build pool to Premium deployments. - **Repeated admonition (28 files under `ai-coder/agent-firewall/` and `ai-coder/ai-gateway/`)**: replaced "requires the AI Governance Add-On / as of Coder v2.32, deployments without the add-on..." with "is part of AI Governance, which is included with a Premium license." The v2.32 add-on gate no longer applies; the gate is now Premium vs. Community. - **`docs/ai-coder/index.md`, `security.md`, `tasks.md`, `usage-data-reporting.md`, `admin/licensing/index.md`, `install/releases/esr-2.29-2.34-upgrade.md`, `ai-gateway/ai-gateway-proxy/setup.md`, `ai-gateway/clients/claude-code.md`**: reworded add-on references to Premium inclusion. - **`docs/manifest.json`**: nav title "AI Governance Add-On" → "AI Governance", updated two descriptions, and swapped the 25 `"state": ["ai governance add-on"]` badges to `["premium"]` so the sidebar badge reads "Premium" instead of "AI Governance Add-On". - **`docs/images/single-region-architecture.png`**: refreshed the diagram in the **Community and Premium editions** tab on [Architecture](https://coder.com/docs/admin/infrastructure/architecture). Also deleted the unreferenced `single-region-architecture.svg` copy. ## Follow-ups outside this PR - The `"ai governance add-on"` doc-state badge is defined in `coder/coder.com` (`src/utils/docs/state.ts`). After this merges, no manifest entry uses that key, so it becomes dead config and can be removed there. - `enterprise/coderd/license/license.go:564-572` still warns admins that "The AI Governance add-on is required to use AI Gateway." That backend string will contradict these docs once shipped. ## Verification - `pnpm run lint-docs`: 0 errors across 504 files - `make lint/emdash`: clean - Vale on the changed Markdown files: 0 errors; remaining warnings are pre-existing gerund headings on untouched lines - `docs/manifest.json` validated as JSON - Confirmed the deleted SVG had no references anywhere in the repo --- PR generated with Coder Agents on behalf of @mattvollmer.
56 lines
2.4 KiB
Markdown
56 lines
2.4 KiB
Markdown
# Run AI Coding Agents in Coder
|
|
|
|
Learn how to run & manage coding agents with Coder, both alongside existing
|
|
workspaces and for background task execution.
|
|
|
|
## Agents in the IDE
|
|
|
|
Coder [integrates with IDEs](../user-guides/workspace-access/index.md) such as
|
|
Cursor, Windsurf, and Zed that include built-in coding agents to work alongside
|
|
developers. Additionally, template admins can
|
|
[pre-install extensions](https://registry.coder.com/modules/coder/vscode-web)
|
|
for agents such as GitHub Copilot.
|
|
|
|
These agents work well inside existing Coder workspaces as they can simply be
|
|
enabled via an extension or are built-into the editor.
|
|
|
|
## Coder Agents
|
|
|
|
In cases where the IDE is secondary, such as prototyping, research, or
|
|
long-running background jobs, [Coder Agents](./agents/index.md) is the
|
|
recommended way to delegate development work to coding agents in your Coder
|
|
deployment.
|
|
|
|
Coder Agents is a native AI coding agent built into Coder. The agent loop runs
|
|
in the Coder control plane on your infrastructure rather than inside the
|
|
workspace, so workspaces can be completely network isolated. Developers
|
|
interact with agents through the web UI or the REST API.
|
|
|
|

|
|
|
|
[Learn more about Coder Agents](./agents/index.md) for architecture details,
|
|
supported LLM providers, and how to get started.
|
|
|
|
## Govern AI activity with AI Governance
|
|
|
|
AI coding tools are quickly becoming core to how engineering teams ship
|
|
software. As adoption grows, platform teams want a clear picture of how AI is
|
|
being used, consistent guardrails across teams, and predictable cost controls
|
|
so they can confidently scale AI tooling to the whole organization.
|
|
|
|
[AI Governance](./ai-governance.md) is included with a Premium license and adds
|
|
observability, management, and policy controls for AI tooling across your
|
|
Coder deployment. It includes:
|
|
|
|
- [AI Gateway](./ai-gateway/index.md) for centralized authentication, audit
|
|
trails of prompts and tool invocations, and policy enforcement against
|
|
upstream LLM providers.
|
|
- [Agent Firewall](./agent-firewall/index.md) for process-level network and
|
|
command policies that restrict what agents can reach and do inside a
|
|
workspace.
|
|
- Expanded Agent Workspace Build allowances for teams running AI-driven
|
|
background work at scale.
|
|
|
|
[Learn more about AI Governance](./ai-governance.md) for use cases, entitlements,
|
|
and how to enable it in your deployment.
|