Keep Cursor’s API keys out of .env files and chats.
The AI code editor, its terminal agent and its cloud agents. With Vando, your keys stay on your phone. When Cursor 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.
Checked against Cursor’s own documentation on 2026-11-10; the guide links its sources.
Set up Cursor in four steps.
-
1 · Install vando and connect it to your phoneIn your own terminal, not through Cursor.
vando connectshows 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 · Tell it how to askPut the note in
AGENTS.mdin the project root (the editor, the Cursor CLI and cloud agents all read it), or in a rule file.cursor/rules/vando.mdcwithalwaysApply: true. -
3 · Let vando run reach your phoneCursor’s agent runs terminal commands in a sandbox whose network is blocked by default. Allow Vando’s server in the project’s
.cursor/sandbox.json(the project file wins over~/.cursor/sandbox.json); put the addressvandonames in its blocked message where the snippet says Vando’s server. Keep the default Auto-review run mode, or use Allowlist and addvando. In the Cursor CLI the allow rule isShell(vando), which matches on the first word, so it allows everyvandosubcommand.{ "networkPolicy": { "default": "deny", "allow": ["<Vando's server>"] } } -
4 · The MCP tools, if you want themOptional. Add the server to
.cursor/mcp.json(this project) or~/.cursor/mcp.json(all projects); the editor and the Cursor CLI share it. Cursor asks before each MCP tool call by default; in the CLI,Mcp(vando:*)is the permission token.{ "mcpServers": { "vando": { "type": "stdio", "command": "vando", "args": ["mcp"] } } }
Use Vando in every project.
Cursor has no user-level instructions file. Its User Rules live in the settings (Customize → Rules), typed as text, and apply across projects; project rules win where they conflict. Put the every-project note there, or in each project’s AGENTS.md.
Put this note there, so Cursor 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 database migration with the connection string.
- You
- Ask Cursor’s agent to run the pending migrations.
- Cursor runs
vando run --secret DATABASE_URL -- pnpm prisma migrate deploy- Cursor shows
- The command in the agent terminal, then “Waiting for your phone”.
- Your phone shows
- “Cursor · MacBook wants to use DATABASE_URL”. Give once; the migration runs with the URL in its environment, and Cursor’s chat never sees it.
In the cloud, or on another computer.
Cursor’s cloud agents run on isolated machines with internet on, install from .cursor/environment.json, and run every terminal command without asking. You can install vando there, but each new machine needs its own connect and nobody reads the code unless you are watching. Don’t store a Vando connection key as a cloud agent secret. Use Vando with the editor or the CLI on a computer you sit at.
Good to know with Cursor.
- Without the
sandbox.jsonrule,vando runfails with a connection error, not exit 75. - The CLI’s Shell Mode has a fixed 30-second timeout, shorter than a phone approval can take: the agent should run the same command again on exit 75.
- Opened from the Dock with
vandoinstalled under nvm, Cursor may not find it: put thePATHline in~/.zshenv, or use the full path as the MCPcommand(a forum tip, not Cursor’s docs). - Heavy shell prompts (Powerlevel10k and the like) can garble the agent terminal; skip them when
CURSOR_AGENTis set. Cursor’s docs don’t say whether the sandbox can reach the keychain, so runvando connectin your own terminal.
Questions.
Why does Cursor’s agent say it can’t reach Vando?
The agent’s sandbox blocks the network by default. Add Vando’s server to networkPolicy.allow in .cursor/sandbox.json; vando names the address in its blocked message.
Which file does Cursor read the note from?
AGENTS.md in the project root, which the editor, the Cursor CLI and cloud agents all read, or a .cursor/rules/vando.mdc rule with alwaysApply: true. There is no user-level file: User Rules live in the settings.
Can Cursor’s cloud agents use Vando?
They can install it, but each machine needs its own connect and nobody is there to read the code. Keep Vando for the editor and the CLI on a computer you sit at, and never store a connection key as a cloud agent secret.
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 →