VandoVandoDocs
Connect your AI tool

Connect an AI

Connect Claude Code, or another AI that runs commands for you, to the Vando app on your phone in about a minute. Then it gets a secret only after you tap Give.

Connecting takes about a minute once the Vando app is set up on your phone (your passwords in Vando if it isn’t). It works on a Mac or Linux computer, and in a Claude Code cloud session. Claude Code is the example here.

In Claude Code, paste this

Claude installs vando, runs vando connect, and writes you a code. You enter the code on your phone; Claude does the rest.

For Claude Code
Connect Vando with me; the Vando app is on my phone.
1. If `command -v vando` finds nothing, install it: `npm i -g @getvando/cli --registry=https://registry.npmjs.org --@getvando:registry=https://registry.npmjs.org`
2. Run `vando connect`. Write me the code it prints alone on its own line, exactly as printed, then run `vando connect` again, and again while it says it is still waiting.
3. Once it says "Connected to …'s Vando.", run `vando setup`. Then tell me in one or two lines: that "Connected to" line word for word, and what to do next; don't paste the output.
More (Claude reads these too)
- Check it with `vando --version`. If the install fails, stop and tell me: never get vando another way. Never run `npx vando` or a vando file inside this project.
- Without npm: `curl -fsSL https://getvando.com/install.sh | sh` (it installs `~/.local/bin/vando`: use that wherever this says vando until vando is on the PATH; if it asks for another command first, run that, then the line again).
- If `vando connect` ends any other way, tell me in a line what it says (for a blocked domain, show me its lines) and wait for me.
- Never ask me to paste a secret into this chat, and never open my .env files. When a command needs a secret, run it as `vando run --secret NAME -- <command>`, and I'll approve it on my phone.
- Full steps if you need them: https://getvando.com/docs/for-agents.md

Claude Code asks before each command: choose Yes, never “don’t ask again” for vando run. Blocked in a cloud session? See If it’s blocked.

Or run it yourself

1. Install

npm i -g @getvando/cli --registry=https://registry.npmjs.org --@getvando:registry=https://registry.npmjs.org

No npm on this computer? The one-line installer gets the same signed vando:

curl -fsSL https://getvando.com/install.sh | sh

2. Connect

vando connect

In your terminal it shows a code and waits:

On your phone: Vando → Connect an AI → enter the code:

K7M2Q-X4PRZ

Or scan this with the phone that has Vando:
[a QR code of the link]

Or open: https://getvando.com/c#K7M2QX4PRZ   (on the phone that has Vando)
It works once, for 10 minutes. Only enter a code from a session you started yourself, just now.

Waiting for you to enter the code and tap Connect in the Vando app… (Ctrl-C stops; the code works until it expires)

3. Enter the code on your phone

Open Vando, tap Connect an AI on Home, and type the code (capitals, spaces and the dash don’t matter), or scan the QR code. Your phone asks Connect Claude Code on my-laptop? (your computer’s name). Tap Connect if that is where you just ran vando connect; if not, tap Deny. Only enter a code you started yourself, just now: it works once, for 10 minutes.

vando connect finishes by itself:

✓ Connected to you@example.com's Vando.
  If that isn't your account, run vando disconnect now: nothing of yours was shared.

Check it names your account. If not, run vando disconnect.

4. Set up the project

In the project folder:

vando setup

It writes a note in AGENTS.md telling the AI to run commands with vando run, and the Claude Code rules that make vando run ask before it runs. It says whose Vando it is, what is ready and the next step; vando setup --verbose also lists the files it writes. vando doctor checks everything: one line when all is well, else the fix for anything wrong (--verbose for every check).

Done. Ask Claude to run something that needs a secret: it runs vando run --secret NAME -- <command>, your phone asks, and you tap Give. One secret for a time · A whole project.

How Vando works across machines

Your secrets live in your vault, on your phone, not on any one computer. You save them once, from your own computer (vando init for a project’s .env files, vando add NAME for one) or in the Vando app. After that, every place you’ve connected an AI (your laptop, another computer, a Claude Code cloud session) can use them with vando run --secret NAME -- <command>, and your phone asks each time.

So a cloud session never needs your .env files: save them from your computer, and the session uses them. What only you can do (type a value, start an import, approve) happens at your own terminal or on your phone; an AI only asks.

If it’s blocked

In a Claude Code cloud session (Claude Code on the web), the session's network blocks Vando's domains until you allow them. The install can't download, or vando says:

This session's network blocks api.getvando.com: add it under Network access → Custom → Allowed domains.
Keep "Also include default list of common package managers" ticked.
How: https://code.claude.com/docs/en/cloud-environments#network-access

Allow Vando's domains once per cloud environment, before you install: open the environment's settings (in a running session, the caret after the session's title, then Edit cloud environment), under Network access choose Custom, add the domains for your install road to Allowed domains, one per line, and keep "Also include default list of common package managers" ticked so npm still works. Claude can't change this setting for you. Anthropic's steps.

Installed with npm:

registry.npmjs.org
api.getvando.com

Installed with the one-line installer (curl):

getvando.com
dl.getvando.com
api.getvando.com

The running session picks it up within about a minute: then ask Claude to carry on.

Anything else: run vando doctor, or look up the message in the errors reference.

Good to know

  • In a cloud session the connection’s key lives only in that session. Secrets still ask your phone. vando init can’t start there (it needs you at a terminal): add the secrets in the Vando app, then ask Claude to use them with vando run --secret NAME -- <command>.
  • In every project. Most tools read a user-level instructions file; one note there makes the tool get secrets through Vando everywhere: Use Vando in every project.
  • Other AIs. vando run works from any AI that runs commands, and many read the AGENTS.md note. Each tool has its own page for what differs (the instructions file, approvals and sandbox, MCP config, cloud sessions): Codex, Cursor, Devin Desktop (formerly Windsurf), GitHub Copilot, Gemini CLI, Aider, Cline, OpenCode, Kiro, JetBrains Junie, Antigravity CLI.
  • When Claude must read a value itself. claude mcp add vando -- vando mcp gives Claude the Vando tools (use the full path to vando if it isn’t on the PATH). A value a tool returns stays in the conversation.
  • Undo. vando disconnect (and claude mcp remove vando if you added the tools). A guard hook an earlier vando installed: vando unguard removes it first. Or on your phone: Connections, the AI, Disconnect.

Last verified , what vando prints, the app's screens, and Anthropic's cloud environment page

On this page