Learn · Step 2 of 7
Devin's four surfaces: Cloud, Desktop, CLI, and Plugins
Devin is not one product. Cloud, Desktop, the CLI, and the Windsurf Plugins line each do different work — and the local agent story changed in 2026.
The single most common source of confusion about Devin is that people talk about it as one thing. It is four, and they are documented separately because they do different work in different places.
Devin Cloud
The hosted agent at app.devin.ai. Devin runs inside a virtual machine that Cognition operates, boots from a snapshot of your configured environment, and works through a task while you watch or walk away.
Cloud is where the orchestration features live — Playbooks, Knowledge, Secrets, and Devin Review. It has two documented modes: Ask, a lightweight mode for exploring a codebase and building a plan without changing code, and Agent, the full autonomous mode.
Devin Desktop
The IDE. This is what used to be called Windsurf; Cognition rebranded it Devin Desktop on 2 June 2026. It ships an agent manager built in, including an Agent Command Center with a Kanban view and “Spaces” for shared context.
It remains backwards-compatible with Windsurf and VS Code extensions, keybindings, and language servers — which matters if you are evaluating a switch and have an editor configuration you do not want to rebuild.
Devin CLI
A local command-line agent that runs in your terminal against your local files, tools, and environment, with integration back into Devin Cloud. It is the surface to reach for when the work is local and you would rather stay in a shell than an IDE.
Windsurf Plugins
The Plugins line brings assistance into editors you already use rather than asking you to move: JetBrains, VS Code, Visual Studio, Vim, NeoVim, Jupyter, and Chrome, among others.
The part that actually changed: Cascade and Devin Local
This is where most out-of-date advice goes wrong, so it is worth being precise.
Cascade was Devin Desktop’s original local agent — Code and Chat modes, tool calling, voice input, checkpoints, linter integration, and a documented ceiling of 20 tool calls per prompt.
Devin Local is its replacement. Cognition describes it as the “next-generation agent harness shared with Devin CLI,” rewritten from scratch in Rust where Cascade was Python, up to 30% more token-efficient, and supporting newer capabilities such as subagents.
Two consequences follow, and they are the reason this section exists:
- Devin Local and the Devin CLI are the same harness. The docs state the CLI “shares the same agent harness as the Devin Local agent.” They are two front doors onto one engine, not two independent agents.
- Cascade’s migration window has closed. Cognition documented Cascade as available “through July 1st” 2026 for incremental migration. That date has passed, so any tutorial that tells you to reach for Cascade is describing a surface you should no longer plan around.
Devin Local was still documented as preview at the time of writing, with limitations relative to Cascade and no support in the JetBrains plugin for Devin Desktop. Cognition has not published an exhaustive list of those limitations, so treat “preview” as literal rather than assuming full parity.
Which one should you use?
- Evaluating Devin at all, or delegating a multi-step task you do not want to babysit → Cloud
- You want an IDE with the agent built in → Desktop
- You live in a terminal → CLI
- You are not willing to leave your current editor → Plugins
References
- Devin Local — docs.devin.ai
- Cascade — docs.devin.ai
- Devin CLI — docs.devin.ai
- Windsurf is now Devin Desktop — devin.ai
- Windsurf Plugins: getting started — docs.devin.ai
From Devin Central — subscribe for Devin news, features & tutorials. Devin is a trademark of Cognition.