Skip to main content

Buyer guide

Moving a Team from Windsurf to Devin Desktop

Device-management approval for the renamed app, the Devin Local home for each Cascade memory, workflow, and command list, and a new path for JetBrains users.

Reading time
2 min read
Sources
11 cited
In this piece
Devin Desktop (formerly Windsurf)+17 Mixed

Approve the renamed Devin Desktop app in device management first, then move Cascade memories, workflows, and command lists to their Devin Local equivalents. Windsurf became Devin Desktop on June 2, 2026, and Devin Local replaced Cascade for new conversations. Engineers on the Windsurf JetBrains plugin need a replacement path.

When you need this

  • Your device-management policy approves an application named Windsurf.
  • Your team built memories, workflows, or terminal command lists around Cascade.
  • You are on an Enterprise plan, where Devin Local stays off until an admin turns it on.
  • Some engineers work in JetBrains IDEs through the Windsurf plugin.

Evaluation criteria

  1. Device management

    Will endpoint security allow the renamed app?

    Look forApprove Devin.app on macOS, Devin.exe on Windows, and devin on Linux. Cognition warns that a policy approving only Windsurf can flag or block the renamed app, and that the team owning those policies is often not the one running the editor rollout. The app reads system-level rules, workflows, skills, and hooks from the Devin directory first, then the legacy Windsurf directory.

  2. Settings and paths

    What carries over, and what moves?

    Look forThe migration copies settings, keybindings, snippets, workspace state, and extensions. It skips caches, logs, and local history. Extensions move from ~/.windsurf/extensions to ~/.devin/extensions, and devin-desktop replaces the surf command. One engineer retained every extension and recommends backing up the old folders first.

  3. Agent choice

    Which agent do engineers start on, and who decides?

    Look forCascade was removed in version 3.9.19 on Sep 8, 2026. Devin Local is the only built-in agent, and the Continue in Devin Local prompt moves existing Cascade conversations. On Enterprise, an admin must turn Devin Local on.

  4. Memories and workflows

    What stops working when engineers switch to Devin Local?

    Look forDevin Local does not support memories, workflows, app deploys, or Arena Mode. The Cascade Migration Wizard moves memories and workflows to skills. Rules and AGENTS.md files keep working, with .devin/rules taking precedence over .windsurf/rules.

  5. Command permissions

    Do your Cascade command lists still protect you?

    Look forDevin Local replaces Cascade's auto-execution levels with allow, ask, and deny rules. Legacy terminal allow and deny lists are enforced only as a fallback until you write an equivalent permission policy.

  6. JetBrains users

    What happens to engineers on the Windsurf JetBrains plugin?

    Look forThe plugin is in maintenance mode, Cascade inside it is being deprecated, and newer JetBrains releases can break it. Cognition recommends running Devin in JetBrains IDEs over ACP (Agent Client Protocol) instead.

Questions to ask vendors

  1. Which build can our admins test before the update reaches every machine?
  2. Which legacy enterprise controls have no Devin Local equivalent, and how do we replace each one?
  3. Does our plan and price stay the same after the move, including any grandfathered Windsurf pricing?
  4. Which Cascade memories and workflows have we not yet moved to skills?
  5. Which hostnames must our firewall allow for updates and remote development?

Red flags

  • The rename handled by the IDE team alone, without the team that owns device-management policies.
  • Cascade memories left in place on the assumption that Devin Local reads them.
  • Terminal command lists treated as the permission policy for Devin Local.
  • JetBrains users left on a plugin in maintenance mode with no replacement plan.

Products in this piece

Sources

Official documentation
9
Public source
2
  1. Devin Desktop changelogOfficial documentationdocs.devin.ai
  2. Devin Desktop docs: FAQ on the move from WindsurfOfficial documentationdocs.devin.ai
  3. Devin Desktop docs: Devin Local agentOfficial documentationdocs.devin.ai
  4. Devin Desktop docs: Cascade overviewOfficial documentationdocs.devin.ai
  5. Devin Desktop docs: Memories and rulesOfficial documentationdocs.devin.ai
  6. Devin Desktop docs: TerminalOfficial documentationdocs.devin.ai
  7. Devin Desktop docs: Admin controls referenceOfficial documentationdocs.devin.ai
  8. Devin Desktop docs: Agent Client ProtocolOfficial documentationdocs.devin.ai
  9. Devin Desktop docs: Quota-based usageOfficial documentationdocs.devin.ai
  10. Edwar Diaz: From Windsurf to Devin Desktop: my first impressions after migrating (Jun 4, 2026)Public sourcedev.to
  11. Maksim Danilchenko: Devin Desktop (ex-Windsurf): Features, Pricing, What Changed (Jun 6, 2026)Public sourcedanilchenko.dev

Keep reading

  1. Buyer guideDevin Desktop Workflow Playbook: Rules, Permissions, and Review for Agent WorkSet committed rules, permission scopes, task size, and verification so Devin Local changes arrive tested and spend stays visible.
  2. Buyer guideDevin Desktop Permissions & Data Controls ChecklistSeven checks for security or compliance teams that must approve the editor before a team rollout, each tied to the plan that offers it.
  3. Buyer guideDelegating from Devin Desktop to Devin CloudKeeping long tasks running after the laptop closes, with local and cloud agents on one feature: six checks before a team relies on it.
Read the research