mirror of
https://github.com/coder/coder.git
synced 2026-09-24 15:04:27 +08:00
Matt Vollmer
5612bb81cb
Updates `docs/ai-coder/index.md`, `docs/ai-coder/best-practices.md`, and `docs/ai-coder/ai-governance.md` to point readers at Coder Agents and the AI Governance Add-On instead of Coder Tasks and Agent Firewall (CODAGT-157). ## Changes - `docs/ai-coder/index.md`: - Rename `## Agents with Coder Tasks` to `## Coder Agents`. Drop the Devin / ChatGPT Codex name-drops and the Tasks pitch. New copy points at `./agents/index.md`, names the agent loop in the control plane, and notes that workspaces can be completely network isolated. Image swapped from `tasks-ui.png` to `agents-hero-image.png` (the hero shot added in #24915). - Replace the `## Secure Your Workflows with Agent Firewall` section with `## Govern AI activity with the AI Governance Add-On`. The new section opens with adoption-first framing (visibility, guardrails, cost) and links to `./ai-governance.md`, with bulleted callouts for AI Gateway, Agent Firewall, and the expanded Agent Workspace Build allowance the add-on bundles. - `docs/ai-coder/best-practices.md`: - In the use-case table, swap `[Tasks](./tasks.md)` to `[Coder Agents](./agents/index.md)` for the developer-led-investigation and prototyping rows, and swap the "Tasks API *(in development)*" cell to `[Coder Agents API](./agents/chats-api.md)` for the background-jobs row. Retitle the Security section link from "securing agents with Coder Tasks" to "securing AI agents" since `security.md` does not actually mention Tasks. Re-ran `markdown-table-formatter` to repad column widths. - In `## Provide Agents with Proper Context`, add a paragraph describing how context is provided in Coder Agents (admin-configured system prompts, centrally registered MCP servers, and skills shipped from repos or templates under `.agents/skills/`), with a transition line clarifying that the existing Memory and Tools subsections cover BYO-agent patterns. - `docs/ai-coder/ai-governance.md`: drop the "Additional Tasks Use (via Agent Workspace Builds)" bullet from the intro feature list and the "Expanding the use of Coder Tasks for AI-driven background work" bullet from the audience list. The `## How Coder Tasks usage is measured` section and the rest of the Tasks-related prose on this page are intentionally left for a follow-up PR. ## Notes for the reviewer - The `[Coder Agents API](./agents/chats-api.md)` link in `best-practices.md` will need to be retargeted if #24830 (which replaces `agents/chats-api.md` with auto-generated `reference/api/chats.md`) lands first. - This is the first slice of the Tasks-references audit. Remaining files (`tasks-core-principles.md`, `tasks-lifecycle.md`, `tasks-migration.md`, `cli.md`, `github-to-tasks.md`, `agent-compatibility.md`, the rest of `ai-governance.md`, `custom-agents.md`, `ai-gateway/clients/claude-code.md`, `manifest.json`, `reference/api/tasks.md`, the `task*` CLI references, the ESR upgrade guide, `feature-stages.md`, `workspace-scheduling.md`, `shared-workspaces.md`) will land in follow-up PRs against the same Linear ticket. Open PRs #24831, #24833, and #24841 cover separate slices and do not touch any file in this PR. - Validation: `markdownlint-cli2`, `markdown-table-formatter`, `scripts/check_emdash.sh`, and `make pre-commit-light` all pass. PR generated with Coder Agents.
57 lines
2.5 KiB
Markdown
57 lines
2.5 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 and Roo Code.
|
|
|
|
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, the CLI (`coder agents`), 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 the AI Governance Add-On
|
|
|
|
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.
|
|
|
|
The [AI Governance Add-On](./ai-governance.md) is a per-user license that 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 the AI Governance Add-On](./ai-governance.md) for use cases,
|
|
entitlements, and how to enable it in your deployment.
|