skip to content

After a Devin Desktop update, a team that came from Windsurf finds new tabs opening Devin Local instead of Cascade: what stops working, and how should they migrate?

level: seniorimportance: should knowfreq 3%

answer

  1. the default agent changed later
  2. four Cascade features left behind
  3. a wizard turns them into skills
  4. approval levels become permission rules
  5. every MCP tool now asks first

basics

~20 s

Devin Local lacks memories, workflows, app deploys and Arena mode; the Cascade Migration Wizard turns memories and workflows into skills. Rules and AGENTS.md keep working, auto-execution levels become allow, ask and deny rules, and MCP tools prompt by default.

solid answer

~50 s

New tabs open Devin Local when nobody has chosen a preferred agent, a default added in v3.6.21 (July 29, 2026); the stable changelog for v3.9.19 (September 8, 2026) then says Cascade has been removed, with a **Continue in Devin Local** prompt for old conversations. Devin Local does not support memories, workflows, app deploys or Arena mode, so the team runs **Devin: Open Cascade Migration Wizard**, which migrates hooks, workflows and memories in one guided flow, turning workflows and memories into skills, with per-item opt-in and previews. Rules, `AGENTS.md` and skills carry over. The approval model changes: Cascade's auto-execution levels and allow and deny lists give way to permission rules where deny beats ask beats allow, set in `.devin/config.json`, per user or by the organisation. Unlike Cascade, Devin Local prompts before any MCP tool by default, offering to allow that tool or its whole server for the session or permanently.

go deeper

for a junior

Recall that new tabs open Devin Local, that it lacks memories, workflows, app deploys and Arena mode, and that a migration wizard turns memories and workflows into skills.

for a middle

Explain what carries over (rules, AGENTS.md, skills, settings), how Cascade's modes map to Normal, Plan and Ask, and where Devin Local reads its config.

for a senior

Show you would run the migration deliberately: review the wizard's skills, rebuild terminal and MCP approvals as deny, ask and allow rules, and check personal global rules still load.

for a principal

Weigh a forced agent change for a whole team: stricter default approvals cost friction but give finer, enforceable control, so decide what to allow centrally before people work around prompts.

## What changed, and when The Devin Desktop rename on June 2, 2026 did not change the agent. The agent change came separately: 1. **April 29, 2026 (v2.1.29)**: the Devin Local agent, the same harness as the Devin CLI terminal agent, could be enabled alongside Cascade. 2. **July 29, 2026 (v3.6.21)**: new tabs began defaulting to Devin Local when no preferred agent was chosen, and the **Devin: Open Cascade Migration Wizard** command arrived. 3. **September 8, 2026 (v3.9.19)**: the stable changelog says Cascade has been removed and Devin Local is the only agent, with a **Continue in Devin Local** prompt to move existing conversations. Several feature pages still document Cascade as the legacy agent, so expect older guidance to read as if both are available. Devin Local inherits the team's Windsurf settings, but it is a different agent with a different approval model. It is also gated by plan: on Team and other non-enterprise plans it is available by default, while on Enterprise plans an admin has to enable the **Devin Local Agent** team setting before members see it in the agent selector. ## What does not carry over | Cascade feature | In Devin Local | What to do | | - | - | - | | Auto-generated memories | not persisted between sessions | migrate critical ones to skills | | Workflows (`/[workflow-name]`) | not available | migrate to skills | | App Deploys | not supported | deploy another way | | Arena mode | not available | none | | Auto-execution levels (Disabled, Allowlist Only, Auto, Turbo) | replaced | write permission rules | The **Cascade Migration Wizard** migrates hooks, workflows and memories in one guided flow, turning workflows and memories into skills, with per-item opt-in and dry-run previews; it skips archived memories. The gap also runs the other way: subagents and plugins exist only in Devin Local, and plan mode and worktree merging reached parity. ## What keeps working - **Rules and `AGENTS.md`.** Devin Local reads them through the Devin CLI rules system: `AGENTS.md`, the legacy `.windsurfrules`, and `.devin/rules/` and `.windsurf/rules/` files with the same `trigger` frontmatter. - **Skills**, in the Devin CLI format; the workspace location is `.devin/skills/`. - **Modes, mapped.** Cascade offered Code, Plan and Ask; Devin Local uses the CLI's agent modes, Normal, Plan and Ask, plus separate permission modes. One check worth making: the Devin CLI rules page documents its personal global rules at `~/.config/devin/AGENTS.md` and `~/.devin/global_rules.md`, not Cascade's `~/.codeium/windsurf/memories/global_rules.md`, so confirm personal rules still load after the switch. ## How approvals change Devin Local replaces auto-execution levels with **permission rules**: - **Deny** rules block an action outright and always win. - **Ask** rules always prompt. - **Allow** rules run without prompting. - With no matching rule, the agent prompts. Rules cover file reads, file writes, command execution, HTTP fetches and MCP tools, and live at project level (`.devin/config.json`, committed), as a local override (`.devin/config.local.json`, gitignored), per user (`~/.config/devin/config.json`) or at organisation level. The default permission mode, **Normal**, auto-approves read-only tools and prompts for edits, shell commands and fetches. By default Devin Local can read and edit only files inside the workspace. For enterprises, the legacy **Auto Run Terminal Commands** setting and the team terminal allow and deny lists stay enforced as a fallback until an enterprise CLI permission config exists; **Restrict Tool Calls to Workspace** has no direct equivalent and is rebuilt with permission rules. ## The MCP difference This is the change that surprises teams most. **Unlike Cascade, Devin Local's default configuration prompts before calling any MCP tool.** The prompt offers to allow the specific tool or every tool on that server, for the session or permanently, and admins can default-allow trusted servers or tools. MCP servers are also configured differently: Cascade used `mcp_config.json`, while Devin Local reads the Devin CLI config files (`.devin/config.json`, `.devin/config.local.json`, `~/.config/devin/config.json`). Why approval gates exist at all is a general agent-safety question; what matters here is that a team's previously silent MCP calls now stop for a decision. ## A migration order that works 1. Run the migration wizard and review each proposed skill. 2. Promote team knowledge from memories into committed rules or `AGENTS.md`. 3. Translate auto-execution settings and terminal lists into permission rules in `.devin/config.json`. 4. Re-register MCP servers in the Devin CLI config and decide which tools to allow up front.

  • Why does an MCP-heavy workflow suddenly need many approvals after moving to Devin Local?
    Devin Local's default configuration prompts before calling any MCP tool, which Cascade did not. Each prompt can allow that tool or the whole server, for the session or permanently, and persisted grants land in config as rules such as `mcp__github__*`. Admins can default-allow trusted servers or tools so they stop prompting across the team.
  • A team relied on Cascade's Turbo auto-execution level. What is the closest setup in Devin Local, and what does Turbo not translate into?
    There is no Turbo in Devin Local; auto-execution levels are replaced by permission rules and modes. Broad allow rules or a more permissive permission mode can reduce prompts, while deny rules keep dangerous commands blocked and always win. Cascade's per-user deny list becomes Deny entries in Devin Local settings or deny rules in the Devin CLI config.
  • Do a team's Cascade conversations disappear when Devin Local becomes the default?
    The Devin Local page says existing Cascade conversations remain available from the history and sidebar, and new conversations never start on Cascade. The v3.9.19 changelog, which says Cascade was removed, points to a Continue in Devin Local prompt for carrying an existing conversation over to the new agent.

  • Devin Local reads Cascade's memories and runs its workflows unchanged.
  • Rules and AGENTS.md must be rewritten in a new format for Devin Local.
  • Cascade's auto-execution level carries over as Devin Local's permission mode.
  • Devin Local calls MCP tools without asking, exactly as Cascade did.
  • An allow rule can override a matching deny rule if it is more specific.
  • The June 2, 2026 rename is what switched new tabs to Devin Local.

Assumes Devin Desktop as documented on 2026-10-04: Devin Local became the new-tab default in v3.6.21 (July 29, 2026), and the v3.9.19 changelog (September 8, 2026) says Cascade was removed.