Windsurf Is Now Devin Desktop: What the June 2 Rebrand, Agent Command Center Default Surface, and Open ACP Protocol Mean for Your AI Coding Stack

By AICoderScope Team · 12 min read
windsurfdevinacpai-codingreviewagentcomparison

TL;DR: Three things actually changed in the Windsurf → Devin Desktop rename: Devin Local replaces Cascade (up to 30% more token efficient, subagent support, Rust rewrite), the Agent Command Center is now the default screen when you open the app instead of the code editor, and the product ships with open Agent Client Protocol support — so you can plug Codex, Claude Agent, or OpenCode directly into it. Pricing held flat. Cascade goes away July 1, 2026.

Devin DesktopCursorClaude Code
Best forTeams managing local + cloud agents from one UISolo devs who live inside an IDETerminal-first autonomous coding tasks
PriceFree / $20 Pro / $200 Max / $40 per user (Teams)Free / $20 Pro / $40 per user (Business)$20 Claude Pro + API token costs
Agent approachMulti-agent command center, ACP-compatibleSingle agent, approval-gatedCLI agent, full filesystem access
The catchACC-first UI takes adjustment; Cascade deprecated July 1No ACP; one agent at a time in editorNo IDE; pure terminal

Honest take: If you are a solo developer who used Windsurf for fast Tab completions and occasional Cascade sessions, nothing meaningful broke on June 2. The real shift is strategic: Cognition is turning Devin Desktop into a fleet manager for AI agents that also happens to contain a code editor. That architecture is right for teams. It is unnecessary complexity for one person shipping a SaaS app.

What actually happened on June 2

Developers who restarted their editor that morning did not get a changelog prompt. The app just opened as “Devin Desktop.” No new download, no manual migration — Cognition pushed the rebrand as a standard over-the-air update.

This was not a surprise for anyone tracking Windsurf’s trajectory. Cognition acquired Codeium (Windsurf’s parent company) in 2025 and spent the following months merging the two product lines. The April 2026 Windsurf 2.0 release was the inflection point: it introduced the Agent Command Center panel and bundled Devin’s cloud agent directly into the editor. June 2 just made the name match what the product had already become.

The domain story is similarly clean: windsurf.com now redirects to devin.ai. The old URL structure is preserved, so bookmarks and documentation links continue to work.

One issue that caught enterprise teams off guard: device management policies. Organizations that had “Windsurf” on their approved software list needed to add “Devin” before June 2 or risk users getting blocked by endpoint management tools when the app phoned home under its new identity. If you manage a team fleet, verify your allowlist before Cascade’s July 1 end-of-life forces everyone to restart.

Devin Local replaces Cascade — the part that actually matters

Cascade launched with Windsurf in late 2023 and became the product’s signature feature: a multi-file agent that could plan, edit, and test across a codebase within a single context window. It was good. Devin Local is a full rewrite, and the architecture difference is meaningful.

The 30% token-efficiency claim. Cognition published this as “up to 30% more token efficient” — the “up to” phrasing is vendor standard for ceiling figures, not medians. Expect real-world gains to be lower in sessions with large codebases and frequent back-and-forth. Still, any directionally real efficiency improvement translates to more quota per dollar at the same plan tier.

Subagents. This is the architectural shift that the token number undersells. Cascade operated as one agent: one context window, one turn, blocking. Devin Local can spawn subagents — purpose-built sub-sessions that handle a defined piece of work in parallel and report back. A task like “update the data layer and write integration tests for the changes” can now have one subagent handling the schema migration while another drafts the test suite, both feeding results back to a coordinator.

For most individual developers writing typical feature work, a single Devin Local session is all you need — you will not feel the subagent ceiling. For teams running parallel PRs or complex refactors across large repos, subagents make the difference between a tool that blocks on tasks and one that actually delegates them.

The Rust rewrite. Cognition rewrote Devin Local in Rust, citing performance as the driver. The observable benefit is startup time and memory footprint, which matters if you are running the local agent alongside other heavy processes (local LLM inference, a dev server, a browser). If you were using Cursor with a local model backend like DeepSeek V4-Flash, you will appreciate that Devin Local is not the reason your RAM is full.

Cascade deprecation checklist (deadline: July 1, 2026)

If you have Cascade-dependent workflows, run through this before July 1:

  1. Automated scripts that invoke Cascade via keyboard shortcuts or macros — remap them to Devin Local triggers in settings.
  2. Team documentation that references Cascade by name — update to Devin Local so new hires are not following dead instructions.
  3. Extension or API integrations (if your team built any) — audit them for Cascade-specific API surface before the endpoint is removed.
  4. Device management allowlists — add “Devin” alongside or instead of “Windsurf.”

Verify the app renamed correctly after the OTA update, especially on managed machines:

# macOS — confirm the application installed as Devin Desktop
ls /Applications/ | grep -i devin
# Expected: Devin Desktop.app

# If still showing as Windsurf.app, force a manual reinstall from windsurf.com
# Windows — PowerShell check for the updated binary
Get-Process | Where-Object { $_.Name -like "*devin*" -or $_.Name -like "*windsurf*" }
# Expected: devin (or Devin Desktop) running; windsurf process should no longer appear post-update

Until July 1, both Cascade and Devin Local coexist in the editor. Run Cascade sessions normally while migrating high-stakes workflows to Devin Local and verifying outputs match expectations.

Agent Command Center as the default surface

The ACC debuted in Windsurf 2.0 (April 2026) as an optional panel: a Kanban view showing all your local and cloud agent sessions in one place. In Devin Desktop, it is what you see when the app opens. The code editor is not gone — you access it the same way you always did — but the product is no longer presenting itself as “an editor with an AI panel attached.” It is presenting as “an agent command center that also contains an editor.”

Spaces are the new organizational layer built around this. A Space groups everything related to a task: agent sessions, the PRs they opened, the files they touched, reference context you want persistent across agents. If you are working on a feature that involves three separate agent sessions over two days, a Space keeps that context available without re-pasting it each time.

For individual developers, Spaces add organizational value without getting in the way. For team leads managing multiple developers each running multiple agents, Spaces become the answer to “how do I know what the agents are doing?”

This shift does have a cost. The ACC-first interface is a genuine context switch from Windsurf’s IDE-first design. Developers who open their editor to immediately see code — not a session board — will need to adjust. The muscle memory for jumping to a file, checking a diff, or starting a quick completion is still there, just one click deeper.

ACP: the open protocol that makes this more than a Windsurf rebrand

The Agent Client Protocol is the detail most coverage has treated as an asterisk. It deserves more attention.

Zed Industries created ACP in August 2025 and released it under the Apache 2.0 license. The pitch: ACP is to AI coding agents what LSP (Language Server Protocol) is to language tooling — a shared spec that lets any conforming agent run inside any conforming editor, without either side building a custom integration. Before ACP, every agent-editor combination required bespoke glue code. With ACP, an agent that speaks the protocol works in every editor that speaks it.

By June 2026, ACP adoption includes Zed (native), JetBrains IDEs (native via AI Assistant), VS Code (via extension), GitHub, Google, and more than 25 AI agents. Devin Desktop at launch supports Codex, Claude Agent, OpenCode, and any other ACP-compatible agent — including ones your team builds internally.

The practical implication: you are no longer locked to Devin Local as your only agent inside Devin Desktop. If Claude Code’s agent handles a class of task better — autonomous test generation, for example — you can run it inside the same interface you use for everything else, sharing the same Spaces context. This is the multi-agent orchestration workflow described in our parallel agents guide made concrete inside a single editor.

If you’ve been running Zed for its ACP-native parallel agents setup (covered in our Zed vs Cursor comparison), Devin Desktop now offers a similar multi-agent surface from a VS Code fork — which matters for teams that rely on VS Code extension compatibility.

What did not change

Pricing. Free, Pro ($20/month), Max ($200/month), and Teams ($40/user/month) plans carried over unchanged from Windsurf. Verify current pricing at devin.ai/pricing before subscribing — these numbers were confirmed accurate as of June 5, 2026, but Cognition has historically iterated on quota structures.

The editor itself. Devin Desktop is still a VS Code fork. Every extension, setting, keybinding, and theme you had in Windsurf survived the OTA update. The language server integrations, the terminal, the debugger — all identical. This is not Cursor’s approach of a mostly-separate codebase; it is incremental.

SWE-1.6 access. Windsurf’s in-house coding model remains available and is still included in the free tier without consuming quota on Tab completions.

Model access. Claude Sonnet, GPT-5, and other premium models remain accessible on Pro and above.

Who should switch, who should stay put

Switch to Devin Desktop if:

  • You are already on Windsurf. The update already happened; Devin Desktop is what you have.
  • You run multiple agent sessions in parallel and want to manage them from one interface.
  • Your team wants the flexibility to swap between Codex, Claude Agent, or OpenCode without changing editors.

Stay on Cursor if:

  • You want the IDE-first, code-first mental model. Cursor still opens to a file, not an agent dashboard.
  • You rely heavily on Cursor’s approval-gated agent workflow and prefer explicit confirmation before any file change.
  • Your team is already invested in Cursor Rules and custom .cursorrules configurations — that infrastructure works well on Cursor and has no direct equivalent in Devin Desktop.

Use Claude Code if:

  • You want full terminal autonomy without a GUI — running in CI, on a remote server, or inside a GitHub Action.
  • You prefer paying per token on the Anthropic API over a flat monthly subscription (possible at lower usage volumes).

The Cursor vs Devin Desktop question ultimately turns on what you are optimizing for. Cursor optimizes for the experience of writing code. Devin Desktop optimizes for the experience of delegating coding tasks. For the majority of working developers, those are not the same thing — and most days, the former is what you need.

FAQ

Is Devin Desktop still free? Yes. The free tier continues with unlimited Tab autocomplete and light agent quota. SWE-1.6 access is included at no cost. See devin.ai/pricing for current quota limits.

Do I need to reinstall anything? No. The rebrand arrived as a standard over-the-air update. Your settings, extensions, and projects are untouched.

Can I still use Cascade? Yes, until July 1, 2026. After that date, Cascade is removed. Devin Local is the replacement, and Cognition has confirmed settings migration is automatic — you do not need to reconfigure Devin Local from scratch.

What is ACP and do I need to do anything to use it? Agent Client Protocol is an open standard for connecting AI agents to editors. Devin Desktop ships with ACP support enabled. To run an ACP-compatible agent like Claude Agent or OpenCode inside Devin Desktop, install it via the agent marketplace in the ACC. No additional configuration is required for agents that have published ACP adapters.

Does this rebrand affect Devin AI (the cloud autonomous agent)? Devin AI (the cloud agent that handles full engineering tasks autonomously) is a separate product with its own ACU-based pricing. Devin Desktop includes access to Devin Cloud sessions as part of its Plans, but Devin AI’s enterprise pricing and ACU billing remain distinct. Check devin.ai/pricing for the current bundling.

My IT department approved “Windsurf” — will Devin Desktop be blocked? Possibly, if your organization uses an application allowlist. Add “Devin” as an approved application name through your endpoint management tool (Jamf, Intune, etc.) before the next device policy sync.

Should I switch from Cursor to Devin Desktop? Only if the multi-agent command center model maps to how you actually work. For pure coding throughput in a single session, Cursor’s inline suggestions and approval-gated agent remain tighter. See the full Cursor vs Claude Code comparison for a breakdown of where each tool wins.

Sources

Last updated June 5, 2026. Pricing and feature details change frequently; verify current state at devin.ai before purchasing.

Was this article helpful?