Cognition rebranded Windsurf as Devin Desktop on 2 June 2026 via a silent over-the-air update — plans, settings, extensions, and keybindings carried over untouched. What didn’t carry over: Cascade, Windsurf’s local agent, which Cognition scheduled for end-of-life exactly one month later, on 1 July 2026. There was no soft deprecation window. Any CI pipeline, automation script, or workflow rule that explicitly invoked Cascade needed repointing to Devin Local before the deadline or it broke.
What replaced it
Devin Local is a ground-up Rust rewrite with parallel subagents, and Cognition claims up to 30% better token efficiency than Cascade. More significant for teams running mixed toolchains: Devin Desktop ships supporting the open Agent Client Protocol (ACP, Apache 2.0 licensed), which means Codex, Claude Agent, Gemini CLI, OpenCode, and Junie can all run as first-class agents inside the same editor rather than being bolted on.
That’s consistent with what we flagged in an earlier signal on tool stacking: AI coding tools aren’t consolidating into one winner. They’re splitting into layers — an editor or terminal as the control surface, with multiple agents plugged in underneath depending on the task. ACP support is Cognition betting that being the best host matters more than being the only agent.
Why the hard cutover matters
A one-month deadline with zero grace period for a tool embedded in CI pipelines is an aggressive migration timeline, even by AI-tooling standards. Teams that treated Cascade as a stable dependency rather than a fast-moving product got a forced migration with no warning runway. That’s a recurring risk with AI dev tooling generally: the tools are improving fast, but “fast-moving” cuts both ways when your build pipeline depends on one of them.
So what
If any part of your delivery pipeline hard-codes a specific AI coding agent, that’s a dependency risk worth reviewing now, not after the next forced migration. We build AI-assisted workflows with that volatility in mind — see how on the AI-assisted development page, or talk to us about de-risking your own toolchain.