Connect Devin Desktop (formerly Windsurf)
Connect Devin Desktop (formerly Windsurf) to the Vando app on your phone, so it gets a secret only after you tap Give, and keys stay out of your .env files and chats.
Windsurf, renamed Devin Desktop in June 2026; its Devin Local agent replaced Cascade. Last checked 2026-11-10, against Devin Desktop (formerly Windsurf)’s own documentation (the links at the end). If a step doesn’t match what you see, tell us. For Claude Code, Connect an AI is the same road.
The steps every tool shares
1. Install vando in your own terminal (not through your AI tool):
npm i -g @getvando/cli --registry=https://registry.npmjs.org --@getvando:registry=https://registry.npmjs.orgNo npm on this computer? The one-line installer gets the same signed vando:
curl -fsSL https://getvando.com/install.sh | sh2. Connect it to your phone. It shows a code that works once, for 10 minutes; open Vando on your phone, then Connect an AI, enter the code and tap Connect. Run vando connect again to finish. Do this in your own terminal: it writes the connection’s key on this computer, and many sandboxes block that.
vando connect3. Save a secret once. Without a terminal it opens a one-time page in your own browser; you paste the value there and it goes to your phone, locked so only the phone can open it. Tap Save on the phone. Or add it in the Vando app.
vando add STRIPE_KEY4. Your tool runs a command with it. Your phone shows what is asked and for how long; you give it or deny it there, and the value goes into that one program’s environment, as the variable STRIPE_KEY.
vando run --secret STRIPE_KEY -- node send.jsA .env line can name a secret instead of holding it, and vando run fills it in when the program starts:
STRIPE_KEY=vando://Work/acme/dev/STRIPE_KEY5. Tell your tool how to ask: put this note in its instructions file (the file is named below):
## Secrets (Vando)
- 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).
- 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.
- Output that shows `[vando:NAME]` had a secret hidden; that is expected.
- Don't use `vando get` or `vando env --reveal`: they print values where you can read them. `vando env` (names only) is fine.
- Never enter a connect code yourself.What differs for Devin Desktop (formerly Windsurf)
The instructions file
Put the note from step 5 in AGENTS.md in the project root (always on), or a rule file in .devin/rules/ (the older .windsurf/rules/ still loads).
Every project: ~/.devin/global_rules.md is injected at the start of every session (the legacy .windsurf/global_rules.md loads only when the .devin one is absent). The note to put there: Use Vando in every project.
Approvals and the sandbox
Devin 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:
{ "permissions": { "allow": ["Exec(vando run)"] } }Use "ask" instead of "allow" if you want Devin’s prompt as well as your phone’s. Devin’s 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) to that list in ~/.config/devin/config.json, and keep network_mode at "full" (the limited mode allows only reads, and Vando needs to post). With the sandbox on, your home folder is read-only, so run vando connect in your own terminal.
MCP tools (optional)
Most work goes through vando run, which keeps secrets out of the chat. Add the tools only when Devin Desktop (formerly Windsurf) must read a value itself; a value a tool returns stays in the conversation (the tools). Add the server to ~/.config/devin/mcp_config.json (all projects), .devin/mcp_config.json (this project), or devin mcp add vando -- vando mcp:
{ "mcpServers": { "vando": { "command": "vando", "args": ["mcp"] } } }Devin’s own pages give two different paths for this file (the other is ~/.codeium/mcp_config.json); after saving, check in the app’s MCP panel that vando appears with its tools. Old Windsurf guides that cite ~/.codeium/windsurf/mcp_config.json describe the retired Cascade agent.
Cloud and remote sessions
Devin Desktop can hand a task to Devin in the cloud, which is 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.
If something goes wrong
- Windsurf became Devin Desktop on 2 June 2026, and the older Cascade agent stopped working after 1 July 2026. Guides for Cascade and “Turbo” auto-run are out of date.
- A non-empty sandbox
allowed_domainslist blocks everything else, including npm. - In Smart mode, installs always prompt, so install
vandoyourself rather than asking the agent. - How long a terminal command may run isn’t documented; rely on exit 75 and a re-run.
- Run
vando doctorin your own terminal: it says what is wrong and the command that fixes it. - If a
vandocommand stops, relay what it says; the line ends with a link to the errors reference.
Sources
What this page is written from:
- Devin Desktop: rules and memories
- Devin: MCP
- Devin: permissions
- Devin: sandbox
- Windsurf is now Devin Desktop
Last verified , Devin Desktop (formerly Windsurf)’s own current documentation (links at the end)
Connect Cursor
Connect Cursor to the Vando app on your phone, so it gets a secret only after you tap Give, and keys stay out of your .env files and chats.
Connect GitHub Copilot
Connect GitHub Copilot to the Vando app on your phone, so it gets a secret only after you tap Give, and keys stay out of your .env files and chats.