Atif Ali
062c0fdd3b
## Summary Cognition (maker of Devin) rebranded the Windsurf Editor as Devin Desktop on June 2, 2026, after acquiring it from Codeium in July 2025. Our docs still referred to the editor as Windsurf and linked to a dead `codeium.com` domain. ## Changes - Renamed `docs/user-guides/workspace-access/windsurf.md` to `devin-desktop.md`, rewritten to lead with Devin Desktop branding, note the Codeium -> Windsurf -> Devin Desktop history, and use current links (`windsurf.com`, `docs.windsurf.com`) instead of dead `codeium.com` ones. - Updated `docs/manifest.json` and `docs/user-guides/workspace-access/index.md` to reference the new page. - Updated remaining Windsurf mentions to Devin Desktop in `docs/ai-coder/ide-agents.md`, `docs/ai-coder/index.md`, `docs/reference/glossary.md`, and `docs/ai-coder/ai-gateway/clients/index.md`. - Added `windsurf.com`/`devin.ai` to `.github/.linkspector.yml` ignore patterns; both rate-limit repeated automated requests with 429s (same class of issue as the `codeium.com`/`marketplace.visualstudio.com` fix in #28203). - Switched every module reference from `windsurf` to the new `devin-desktop` registry module (`docs/about/contributing/modules.md`, the three `get-started/customize-your-template/*.md` Terraform tutorials, and the main doc page's module link), since the new module actually renders `display_name = "Devin Desktop"` / `slug = "devin-desktop"` in the UI (the old `windsurf` module hardcodes "Windsurf Editor"). <details> <summary>Scope notes / sequencing</summary> The `devin-desktop` module referenced here is being added in [coder/registry#1050](https://github.com/coder/registry/pull/1050) (not yet merged/released). That PR is itself gated on [coder/coder#28214](https://github.com/coder/coder/pull/28214) (whitelisting the `devin:` URI scheme) shipping in a released Coder version first. This docs PR can merge independently, the module link will 404 until #1050 is released, same as any docs-ahead-of-registry-release sequencing. The Terraform code samples now show `module "devin-desktop"` because that module's `display_name`/`slug` are properly parameterized (unlike `windsurf`, which hardcodes "Windsurf Editor"/`windsurf` regardless of what's passed in), so the docs stay accurate to the rendered UI. </details> ## Validation - `make lint` (docs lint, markdownlint, repo checks) passes. - Manually verified the new outbound links (`docs.windsurf.com`) return 200; `windsurf.com`/`devin.ai` are rate-limited (429) from this environment too, hence the added ignore patterns. Stacked on #28203 (targets that branch so the diff here stays scoped to the rebrand; will retarget to `main` once #28203 merges). > 🤖 This PR was created with the help of Coder Agents, and needs a human review. 🧑💻
2.4 KiB
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 such as Cursor, Devin Desktop, and Zed that include built-in coding agents to work alongside developers. Additionally, template admins can pre-install extensions 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 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 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 is included with a Premium license and adds observability, management, and policy controls for AI tooling across your Coder deployment. It includes:
- AI Gateway for centralized authentication, audit trails of prompts and tool invocations, and policy enforcement against upstream LLM providers.
- Agent Firewall 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 for use cases, entitlements, and how to enable it in your deployment.