Cascade, the Python-based local agent that powered Windsurf for two years, is gone as of today. Cognition shipped the Windsurf-to-Devin-Desktop rebrand on June 2 as a silent over-the-air update, and most developers noticed their editor looked slightly different and kept working. What many missed: Cascade itself had a hard end-of-life date baked into the release announcement. That date is July 1. If your CI pipeline or any automation script calls “Cascade” by name, it stopped working overnight. There is no grace period, no soft deprecation with warnings, no extended support tier. The agent is simply gone.
What Actually Broke (and What Didn’t) #
This is the part Cognition could have communicated better. The interactive in-editor migration was seamless—settings, workspace configs, and your .windsurfrules
files all carried over automatically on June 2. If you only ever used Windsurf interactively, you may not notice anything wrong today.
But if you have automation that explicitly invokes Cascade—CI pipelines, Makefiles, shell scripts, GitHub Actions workflows—those did not migrate. The editor rebrand is automatic. The agent invocation is not. Teams that set up a Cascade-based automated code review step three months ago and have not touched it since will discover a broken pipeline today.
The failure mode is almost deliberately inconspicuous: no deprecation warning in logs, no heads-up email, just a “command not found” or equivalent depending on how you were calling it. A green build on June 30 can be a broken build on July 1.
Find the Breakage Now #
Start with a targeted search across your CI configuration files. Look for case-insensitive matches on “cascade” in the places that matter:
grep -ri "cascade" .github/ .circleci/ Makefile scripts/ 2>/dev/null
grep -ri "cascade" .gitlab-ci.yml .travis.yml .circleci/config.yml 2>/dev/null
Any match in a CI config is a live breakage. For each one, replace the Cascade invocation with the Devin Local entrypoint:
devin acp
acpx --agent './bin/dev-acp --profile ci' 'describe your task'
The acpx CLI is an open-source headless client for Agent Client Protocol sessions—it is what you want for scripted, non-interactive CI use cases where you need an agent to execute a task and return output programmatically.
What Devin Local Is (It’s Not Just a Rename) #
Devin Local is a complete Rust rewrite of Cascade, which was Python. Cognition claims up to 30% better token efficiency—and at least on representative tasks, the numbers look plausible: a medium-sized refactoring task that consumed around 24,000 tokens under Cascade came in at roughly 18,000 under Devin Local. No independent benchmark has confirmed this at scale yet, so treat the 30% as directionally useful rather than a hard guarantee.
The architecturally meaningful addition is subagent support. Cascade was a single-context agent: one task, sequential execution, no delegation. Devin Local can spawn parallel sub-sessions for separable work. Ask it to refactor the data layer and update tests simultaneously, and it can dispatch one sub-session for the schema changes and another for the test suite, with both reporting back to a coordinator. Two modes:
Foreground subagents the parent and wait; you can approve or deny tool calls as they surface.Background subagents run in parallel while the parent continues; only pre-approved tools are allowed, and background agents cannot request new permissions mid-run.
In practice, automatic subagent dispatch works on roughly 40% of multi-step tasks in early testing—a maturing feature, not a finished one. Tasks with clearly separable subtasks benefit most; tightly coupled work still runs better as a single context.
The Bigger Picture: Why Cognition Did This #
The Devin Desktop rebrand is not window dressing. Cognition is betting that the IDE should be an agent command center—a surface for managing fleets of AI coders—rather than a code editor with AI bolted on. Cascade, as a Python single-agent runtime, was not built for that model. Devin Local, as a Rust multi-agent runtime with ACP support, is.
ACP (Agent Client Protocol) is JSON-RPC 2.0 over stdin/stdout—think of it as LSP for AI coding agents. Devin Desktop ships with ACP support out of the box, meaning you can run Codex, Claude Agent, OpenCode, or your own internal agent inside Devin Desktop. You are not locked to Devin Local. The editor becomes the orchestration layer; the agent is pluggable.
The official rebrand announcement frames this as “the IDE becoming the agent command center,” and for once that framing is accurate rather than just marketing language. Whether that vision plays out depends on ACP adoption—JetBrains, Google, and GitHub are already on board, which is a reasonable start.
Action Summary #
If you used Windsurf only interactively, today changes nothing for you. If you automated anything with Cascade, your action items are straightforward:
- Grep CI configs and scripts for “cascade”—any hit is a broken invocation.
- Repoint to
devin acp
for interactive-equivalent workflows. - Use
acpxfor headless CI use cases. - Your
.windsurfrules
files are fine—leave them alone or migrate to.devin/rules/
at your leisure.
Cascade served its purpose. Devin Local is a real improvement. The problem is not the replacement—it is the silent cutover on a tool many teams had embedded quietly in CI and forgotten about. Do the search now.