Windsurf 2.0 integrates Devin for cloud agents that keep running after the IDE closes

• Cognition's launch thread positioned Windsurf 2.0 around a split model: local agents for interactive work, cloud agents for work that keeps running after you leave the editor.
• According to Cognition's linked post, Devin runs in its own cloud environment, can work for minutes or hours, opens PRs, runs tests, and QAs its own work with computer vision before handing results back.
• dabit3's summary added two practical details the launch thread only hinted at: cloud agents can run in parallel and can span multiple codebases.
• swyx's launch-day note tied Windsurf 2.0 to a new "Spaces" concept, framing it as a manager layer for agents that compose and coordinate other agents.

You can read Windsurf's launch post, compare it with Cognition's own Devin writeup, and see that at least one Devin feature already has product docs in Windsurf's DeepWiki page. The weird extra reveal came from swyx's screenshot, which shows Slack mockups for Spaces and a feed view from three months ago.

Windsurf's official framing is that 2.0 turns the IDE into a control surface for both interactive and long-running agents, not just a chat pane with better autocomplete. Windsurf's launch post names that layer the Agent Command Center, while Cognition's tweet compresses the product pitch into one sentence about local and cloud agents living together.

That distinction is the whole launch. Local agents stay in your editing loop. Cloud agents keep going after you close the laptop, and dabit3 says they can run in parallel across codebases and stay reachable from any internet-connected device.

The clearest new workflow detail came from Cognition's linked post, which describes a one-click handoff from local planning inside Windsurf to a fresh Devin compute environment in the cloud. That post says Devin can implement the plan, open a PR, run tests, perform QA, and self-review or auto-fix before you inspect the result back in Windsurf.

Cognition's writeup adds one technical claim that stands out in a market full of "agent" marketing: Devin is supposed to handle the async valley between prompt and finished change by working in its own infrastructure for minutes or hours. The same post also says QA can include computer-vision-assisted checks, which pushes the feature past pure code generation and into browser or UI verification work.

Windsurf's docs already show one Devin capability crossing into the editor surface. The DeepWiki docs say Windsurf has implemented Devin's DeepWiki feature for symbol-level code explanations in the sidebar and on hover.

The launch did not just add a cloud execution target. swyx's commentary says the bigger idea behind the new Spaces concept is agent composition, with boss agents that manage and query other agents.

His attached screenshot shows a Slack-era wireframe labeled "Windsurf Spaces / 2.0" with a feed, action-required cards, an email assistant, and pinned spaces. That makes Spaces look less like a single task runner and more like a shared inbox for delegated work.

One small product breadcrumb reinforces that broader merger: the DeepWiki docs explicitly call DeepWiki a Devin feature implemented inside Windsurf. The product line between IDE features and cloud-agent features is getting blurrier by design.