Cognition shipped Devin Desktop last week — and on the surface, it looks like a rebrand of Windsurf. But under the hood, it’s something more consequential: the first major attempt to turn the IDE from a code editor with AI bolted on into a command center for managing multiple AI coding agents simultaneously.
The product launched as an over-the-air update on June 2, with the formal announcement following on June 7. Existing Windsurf users woke up to a new name, a new default interface, and a new local agent engine — but the same credentials, settings, and extensions.
Devin Local: Cascade Gets a Rust Rewrite
The most immediate change for existing users is Devin Local, a complete rewrite of Cascade (the old Windsurf agent) in Rust. Cognition claims it’s “up to 30% more token-efficient” — which translates directly into lower API costs and faster sessions for high-volume users.
More importantly, Devin Local introduces subagent support: it can spawn parallel sub-sessions that report back to the main agent, mirroring the multi-agent architecture Devin Cloud has been using. Cascade, written in Python, will be deprecated and removed on July 1, 2026.
ACP: The Protocol That Changes Everything
The real strategic move is Agent Client Protocol (ACP) support. ACP is an open-source protocol — think “LSP for AI coding agents” — that connects any compatible AI coder to any compatible editor. Created by Zed Industries in August 2025 and already adopted by JetBrains, Google, and GitHub, ACP now gets its biggest endorsement yet.
At launch, Devin Desktop supports Codex CLI, Claude Agent, OpenCode, and any custom ACP-compatible agent. These third-party agents appear in the same Kanban dashboard, share context through Spaces (a new project-level context layer), and operate with the same controls as native Devin sessions.
This is unprecedented. You can now dispatch a Claude Agent to refactor a legacy module, a Codex agent to write tests, and Devin Local to handle the integration layer — all from the same interface, with shared awareness of the project’s files, PRs, and context.
The Paradigm Shift: Developer as Fleet Manager
Theodor Marcu, Head of Product Growth at Cognition, framed it bluntly: “The question for engineering leaders is no longer whether to use AI — it is how to manage a growing fleet of agents working across their organisation simultaneously.”
The default interface in Devin Desktop reflects this. The Agent Command Center — a Kanban view of all active sessions — is what you see first. Code comes second. The editor is still there, fully accessible, but the implicit message is clear: your primary job is no longer typing syntax; it’s orchestrating the agents that produce it.
This shift from “AI-as-accelerator” to “AI-as-actor” has been discussed theoretically for months. Cognition is the first to ship it as a real product.
Spaces and the Agent Router (Coming Soon)
Two features still in the pipeline round out the vision:
-
Spaces — Groups agents, sessions, pull requests, and files by project. Shared context persists across sessions, so agents don’t rebuild their understanding from scratch. Early feature, expected to evolve through Q3 2026.
-
Agent Router — Will direct incoming tasks to the most efficient agent/model based on performance and cost. Organizations can configure routing to reserve expensive models for complex work and cheaper ones for boilerplate.
The Bigger Picture
Cognition’s move validates a trend we’ve been tracking: the coding agent market is maturing from solo assistants into orchestrated fleets. Devin Desktop doesn’t just manage Cognition’s own agent — it manages any ACP-compatible agent, making it a platform play rather than a point solution.
Endorsements from Ramp, Harvey AI, NVIDIA, and Modal suggest enterprise appetite for multi-agent coordination is real. Pricing and security controls remain undisclosed, but the strategic direction is set: the IDE is becoming a management console, and the developer is becoming a fleet commander.
Sources: Tech Edition, ChatForest