new post for testing

Administrator in Optimize May 13 / 1 month ago

Windsurf launched as the first agentic IDE — a code editor where you and your agent work side-by-side on the same codebase.

Since then, agents have gotten much more powerful. The best engineers aren't pairing with a single agent anymore. They're running dozens of agents in parallel across cloud and local environments, on different parts of the same project. While the IDE was built for hands-on work, managing a fleet of agents is an entirely different job.

This creates a new problem. The more agents you manage, the faster you hit the limits of your own attention and working memory.

Windsurf 2.0 is designed to raise that ceiling. We built the Agent Command Center and brought Devin, our autonomous cloud agent, directly into Windsurf so you can do the work of a whole team without one.

The Agent Command Center

The Agent Command Center is a new surface inside Windsurf. It shows every agent you're running, local and cloud, in a single Kanban view, organized by status.

The Kanban view is an intentional design choice. As agents become more capable, the engineer's job shifts from writing code to directing work. You need to see what agent is working on what, what is blocked, and what's ready for review. The interface should reflect that.

The command center doesn't replace the IDE. It's deeply integrated with the existing Windsurf editor features, so you can always make last mile edits manually.

Windsurf Spaces

Spaces are how you organize work in the Agent Command Center.

A Space groups everything related to a specific task or project into a single view: agent sessions, PRs, files, and context. An "Onboarding Flow Redesign" space might have one local session prototyping the UI and two cloud sessions handling API changes and writing tests.