Keep Devin Desktop’s API keys out of .env files and chats.

Windsurf, renamed Devin Desktop in June 2026; its Devin Local agent replaced Cascade. With Vando, your keys stay on your phone. When Devin Desktop (formerly Windsurf) needs one, your phone shows who is asking and why, and you give it just what it asked for, for one run or a set time, or you deny it with one tap.

The Devin Desktop (formerly Windsurf) guide, step by step

Checked against Devin Desktop’s own documentation on 2026-11-10; the guide links its sources.

Set up Devin Desktop (formerly Windsurf) in four steps.

  1. 1 · Install vando and connect it to your phoneIn your own terminal, not through Devin Desktop (formerly Windsurf). vando connect shows a code; open Vando on your phone, tap Connect an AI, enter it and tap Connect. The code works once, for 10 minutes.
    $ npm i -g @getvando/cli --registry=https://registry.npmjs.org --@getvando:registry=https://registry.npmjs.org
    $ vando connect
  2. 2 · Tell it how to askPut the note in AGENTS.md in the project root (always on), or in a rule file in .devin/rules/. The older .windsurf/rules/ still loads.
  3. 3 · Let vando run reach your phoneDevin Local asks before commands that no rule covers. To let vando run through its own prompt (your phone still asks), add a permission rule to .devin/config.json; use "ask" instead of "allow" to keep Devin’s prompt as well. The sandbox is off by default. If you turn it on and set allowed_domains, every other domain is blocked, so add Vando’s server (the address vando names in its blocked message) in ~/.config/devin/config.json, and keep network_mode at "full": the limited mode allows only reads, and Vando needs to post.
    { "permissions": { "allow": ["Exec(vando run)"] } }
  4. 4 · The MCP tools, if you want themOptional. Add the server to ~/.config/devin/mcp_config.json (all projects) or .devin/mcp_config.json (this project), or run devin mcp add vando -- vando mcp. Devin’s pages give two paths for this file (the other is ~/.codeium/mcp_config.json); after saving, check the app’s MCP panel shows vando with its tools.
    { "mcpServers": { "vando": { "command": "vando", "args": ["mcp"] } } }

Use Vando in every project.

Devin Desktop (formerly Windsurf) reads ~/.devin/global_rules.md in every project. Injected at the start of every session. The legacy .windsurf/global_rules.md still imports, but when both exist only the .devin one loads. Devin’s docs don’t say how it ranks against workspace rules. (Devin Desktop’s rules and memories docs.)

Put this note there, so Devin Desktop (formerly Windsurf) gets secrets through Vando everywhere, suggests vando add in a new project, and suggests moving a project’s .env files into Vando when it finds them:

## Secrets (Vando), in every project
- Never open, print, copy or edit `.env*` files or secret values, and never put a secret in chat.
- Run anything that needs a secret as `vando run --secret NAME -- <command>` (repeat `--secret` for more than one).
- In a new project, keep secrets in Vando from the start: suggest `vando add NAME` for each one, then `vando run` to use it.
- In a project that has `.env` files with values in them, suggest `vando init`: it moves them into Vando with one Save on the owner's phone, so the values stop living in plain files that you and other tools can read.
- Exit 75 means it is waiting for the owner's phone: say "Approve NAME on your phone, then I'll run it again", do other work, then run the same command again. After two waits, stop and tell the owner to open Vando on their phone (the request is in the Inbox).
- Exit 77 means the owner said no or the access ended: don't retry; ask the owner.

An example: A test run that needs an API key.

You
Ask Devin Local to run the integration tests.
Devin runs
vando run --secret OPENAI_API_KEY -- pnpm test:integration
Devin shows
Its permission prompt unless your rule allows it, then “Waiting for your phone”.
Your phone shows
“Devin Desktop · MacBook wants to use OPENAI_API_KEY”. Give once; the tests run with the key in their environment.

In the cloud, or on another computer.

Devin Desktop can hand a task to Devin in the cloud, a separate product with its own environment. Vando needs a connect that someone reads the code for, so use Vando with Devin Local on a computer you sit at.

Good to know with Devin Desktop (formerly Windsurf).

Questions.

Does this page cover Windsurf and Cascade?

It covers Devin Desktop, which Windsurf became in June 2026, and its Devin Local agent, which replaced Cascade. Cascade stopped working after 1 July 2026, so Cascade-era guides don’t apply.

Where does Devin keep the rule that lets vando run through?

In .devin/config.json, as "Exec(vando run)" under permissions.allow. Use "ask" instead of "allow" if you want Devin’s prompt as well as your phone’s.

Which mcp_config.json is the right one?

Devin’s pages give two paths: ~/.config/devin/mcp_config.json and ~/.codeium/mcp_config.json. Save, then check the app’s MCP panel lists vando with its tools; the project file is .devin/mcp_config.json.

What Vando is, in short.

One app on your phone for your passwords, 2FA codes, recovery kits, files and developer secrets. Each thing gets its own lock: Easy, Just me, Two devices or Fort Knox, from a quick tap up to your fingerprint plus a security key. Your laptop and your AI tools hold no keys; when one needs a login or a key, your phone shows who is asking and for what, and you say yes or no there. Every yes is signed on your phone and kept on record.

How the locks work → · The detail for developers → · Every AI tool you can set up with Vando → · Get the app →