Documentation Index
Fetch the complete documentation index at: https://docs.devin.ai/llms.txt
Use this file to discover all available pages before exploring further.
On June 2, 2026, Windsurf is becoming Devin Desktop. This FAQ covers what’s changing, what’s not, and what it means for your team.
What is Devin Desktop?
Devin Desktop is the new name for Windsurf. It’s the same IDE, same editor, and has the same features, but unified under the Devin brand. If you’ve been using Windsurf 2.0, you’ve already been using what will become Devin Desktop.
The Agent Command Center (Spaces, Kanban view, multi-agent management) is now front and center. The classic Windsurf experience (editor, extensions, keybindings, workflows, LSPs) is still there and fully accessible. Nothing is getting removed.
When is this happening?
June 2, 2026. Devin Desktop will be delivered as a regular over-the-air update. You’ll receive a heads up that the experience is changing.
What’s changing?
Windsurf becomes Devin Desktop, with the Agent Command Center as the primary view. The full Windsurf IDE is still available, with all the features you know and love - and all your existing work and progress will remain intact. No ongoing work will have any interruptions, and after a quick orientation, the interface will feel immediately familiar.
Why is this happening?
We’re unifying all of our products under the Devin brand: Devin Cloud, Devin Desktop, Devin CLI, and Devin Review. We believe the future of software engineering is managing teams of agents (local and cloud) working alongside you. Devin Desktop is the command center for that and where we expect developers to spend 90%+ of their days.
Does my plan or pricing change?
No. Your current plan continues to work exactly as it does today. Pricing is unchanged. This applies to all plan types, including legacy Windsurf Enterprise plans.
Do I need to use Devin to use Devin Desktop?
No - you can continue using Devin Desktop with local-only agents.
No. Devin Desktop works out of the box for all existing Windsurf users, including legacy Enterprise customers. Devin Cloud remains a separate SKU. If you’re interested in Devin Cloud, talk to your account team.
What happens to my settings and configuration?
All of your Windsurf settings will be ported to Devin Desktop automatically. Devin Local also inherits your Windsurf settings. If you’re on a legacy Windsurf plan, you can still use windsurf.com to manage your settings.
Will I lose access to anything?
No. The Windsurf IDE, your extensions, your workflows and everything is still there. Your plan, pricing, and access remain the same. Only the name and branding are changing.
For details on how the new Devin Local agent handles features like memories and workflows, see its limitations.
Are my Windsurf rules still supported? What about Devin rules?
Yes. Devin Desktop continues to read all of your existing Windsurf rules, and adds support for the new .devin/ equivalents. Nothing you have today needs to change.
Both rule formats are supported side by side:
- Single-file rules: the legacy
.windsurfrules file at your workspace root is still read. (There is no .devinrules single-file equivalent — use the directory format below for new rules.)
- Directory rules: individual
.md rule files under a rules/ directory. .devin/rules/ is the preferred location and takes precedence, with .windsurf/rules/ kept as a fallback for backward compatibility.
In addition, Devin Desktop reads rules from AGENTS.md / agents.md files, and can import .cursor/rules (.mdc) into .devin/rules/. Directory-based rules support activation triggers in their frontmatter (always-on, model-decision, glob-based, and manual), so a rule can apply to every request, only when the model decides it’s relevant, only for files matching a glob, or only when invoked manually.
Enterprise admins can also deploy rules system-wide; see System-level configuration below.
What is Devin Local?
Devin Local is a new local agent available in Devin Desktop. It’s more efficient than Cascade, supports subagents, and runs the same architecture as Devin CLI. Devin Local inherits your existing Windsurf settings.
What happens to Cascade?
The local agent is also being brought under the Devin brand and will be called Devin Local, and comes with an improved harness, up to 30% better token efficiency, subagent support, and sandboxing. Starting June 2nd, Devin Local will be the default. Cascade remains available through July 1st.
Will my pricing change when switching to Devin Local?
No, Devin Local inside Windsurf or Devin Desktop uses the exact same pricing model as Cascade: if you are currently using prompt-based credits, you will continue to do so.
What about Windsurf JetBrains?
The Windsurf JetBrains plugin is not affected by this change and will continue to work as expected (and will keep its name).
What happens with previous Windsurf releases?
As a general rule, we consider every release but the latest to be deprecated, although we do our best to maintain compatibility and not break previous versions. This follows the same model as Microsoft’s VSCode. You will be able to continue to download previous Windsurf releases, although we don’t recommend it.
Can our admins test this before the rollout?
Yes. We’re happy to share an early build with your admins in the week before June 2 so they can validate the change in your environment ahead of the org-wide rollout. Reach out to your account team to coordinate.
Will we need to update our network allowlist?
No network changes are required.
For Cognition Platform users who log in via devinenterprise.com, all authentication and settings will be managed from the Devin website.
For Legacy Windsurf Enterprises, no changes are strictly required. Updates and binaries will continue to be stored on codeiumdata.com and login will continue to happen on windsurf.com/enterprise. The only change is that user-facing website content (the changelog and documentation) will be moving to a Devin subdomain (docs.devin.ai). If you want your team to keep access to the changelog and docs, add docs.devin.ai or docs.devinenterprise.com to your allowlist (or .devin.ai / .devinenterprise.com if you use wildcard rules).
What is the full list of hostnames we should allow?
No whitelist changes are required before launch.
If you prefer to whitelist proactively, these are the relevant hostnames:
All customers (updates, binary downloads, and remote development):
.codeiumdata.comupdate.windsurf.com.windsurf.com.codeium.com.googleapis.com (authentication)apis.google.com (authentication)decagon.ai (support)docs.devin.ai or docs.devinenterprise.com (changelog and documentation, after June 2, 2026)
Additionally, Cognition Platform customers should whitelist .devin.ai or .devinenterprise.com
What hostnames does the desktop application use for automatic updates?
The desktop application checks for and downloads OTA (over-the-air) updates automatically. The update system uses two types of requests:
- Update check API: the application periodically contacts the update server to see if a new version is available.
- Some users disable this feature
- Binary download: when an update is found, the application downloads the new installer or archive from a CDN.
The relevant hostnames are used by all customers (both Legacy Windsurf and Cognition Platform):
update.windsurf.com — update check APIwindsurf-stable.codeiumdata.com — binary downloads for the stable and next channels
If your firewall or proxy rules are domain-based, ensure these hostnames are reachable on port 443 (HTTPS). Blocking them will prevent the application from detecting or installing updates.
What hostnames are used for remote development (SSH, Dev Containers)?
When connecting to a remote machine via SSH or Dev Containers, the desktop application downloads the Remote Extension Host (REH) and CLI binaries to the remote machine. These hostnames are required for all customers (both Legacy Windsurf and Cognition Platform):
windsurf-stable.codeiumdata.com — REH and CLI archives (stable/next channels)windsurf-nightly.codeiumdata.com — REH and CLI archives (insiders channel)
The remote machine must be able to reach these hostnames on port 443. If your remote servers are behind a corporate proxy or airgapped network, ensure these domains are reachable or pre-stage the REH bundle manually.
Will the app name change affect our device management (MDM) policies?
Yes - this is the most important item for IT and endpoint security teams. The desktop application name is changing from Windsurf to Devin (appearing as Devin.app on macOS, Devin.exe on Windows, and Devin / devin on Linux). Many organizations use central device management (MDM / endpoint management) policies that flag or block any application that isn’t explicitly approved, so a policy that only allows “Windsurf” today may flag or block the renamed application after the June 2 update.
Action required: Before June 2, 2026, add Devin to the allowlist in your device management / endpoint management policies, and confirm with your endpoint security team that the renamed application is approved. Please make sure this reaches the team that actually owns these policies - in many enterprises that team is separate from the one managing the IDE rollout.
What local file paths does the application read from and write to?
Devin Desktop reads from both legacy (Windsurf/Codeium) and new (Devin) file paths during the transition period, and writes new data to the Devin paths. Enterprise admins managing endpoint policies, file integrity monitoring, or data-loss-prevention rules should be aware of the following directories.
All data from legacy paths will be copied over to new paths when Devin Desktop runs for the first time.
Per-user IDE data (settings, extensions, workspaces)
This is the VS Code-derived user data directory. If the new path exists, we will read from it:
| OS | Legacy path (read) | New path (read + write) |
|---|
| macOS | ~/Library/Application Support/Windsurf/ | ~/Library/Application Support/Devin/ |
| Windows | %APPDATA%\Windsurf\ | %APPDATA%\Devin\ |
| Linux | ~/.config/Windsurf/ | ~/.config/Devin/ |
User/settings.json, User/keybindings.json, User/snippets/, globalStorage/, Workspaces/, argv.json
Per-user extensions directory
Extensions are stored in the dot-folder derived from the product name. Legacy paths will remain read-only:
| Legacy path (read) | New path (read + write) |
|---|
~/.windsurf/extensions/ | ~/.devin/extensions/ |
Per-user configuration directory
The primary user-level configuration directory stores user settings, MCP config, global skills, and workflows:
| Purpose | Path |
|---|
| User settings | ~/.codeium/user_settings.pb |
| MCP config | ~/.codeium/mcp_config.json |
| Global workflows | ~/.codeium/windsurf/global_workflows/ |
| Global skills | ~/.codeium/windsurf/skills/ |
| CLI binaries | ~/.codeium/windsurf/bin/ |
The ~/.codeium/ directory structure is not changing in this release. These paths remain the same.
System-level configuration (admin-managed, per-machine)
Enterprise admins can deploy rules, workflows, and skills system-wide in these directories:
| OS | Legacy path (read) | New path (read + write) |
|---|
| macOS | /Library/Application Support/Windsurf/ | /Library/Application Support/Devin/ |
| Windows | C:\ProgramData\Windsurf\ | C:\ProgramData\Devin\ |
| Linux | /etc/windsurf/ | /etc/devin/ |
rules/, workflows/, skills/
CLI / shell command binaries
| OS | Path | Binary names |
|---|
| macOS / Linux | ~/.codeium/windsurf/bin/ | devin-desktop, surf (legacy), windsurf (legacy) |
| macOS / Linux | ~/.local/bin/ | devin |
| Windows | %LOCALAPPDATA%\devin\bin\ | devin.exe |
Workspace-level directories (inside repositories)
The application already supports .devin/ as the primary workspace directory and falls back to .windsurf/ for backward compatibility. No admin action is needed for these:
| Legacy (read, fallback) | New (read + write, preferred) | Contents |
|---|
.windsurfrules (root file) | .devin/rules/ (directory) | Project rules (single-file legacy format) |
.windsurf/rules/ | .devin/rules/ | Project rules |
.windsurf/workflows/ | .devin/workflows/ | Workflows |
.windsurf/skills/ | .devin/skills/ | Skills |
.windsurf/plans/ | .devin/plans/ | Plans |
.codeiumignore / .windsurfignore | .codeiumignore (unchanged) / .windsurfignore | Ignore patterns |
What should endpoint security / DLP policies allow?
If your organization uses endpoint security tools that restrict which directories applications can read from or write to, ensure the following paths are permitted for the Devin Desktop application:
- macOS:
~/Library/Application Support/Devin/, ~/.devin/, ~/.codeium/, ~/.windsurf/, ~/.local/bin/devin
- Windows:
%APPDATA%\Devin\, %LOCALAPPDATA%\devin\, ~\.codeium\, ~\.windsurf\
- Linux:
~/.config/Devin/, ~/.devin/, ~/.codeium/, ~/.windsurf/, /etc/devin/, ~/.local/bin/devin
The application also uses the system temp directory ($TMPDIR / %TEMP%) for ephemeral data.
What hostnames does Devin CLI use for updates?
The Devin CLI has its own update mechanism, separate from the desktop application. This change will have no impact to Devin CLI.
Reach out to your account team or customer support.