VandoVandoDocs
Connect your AI tool

Connect Gemini CLI

Connect Gemini CLI 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.

Google’s command-line coding agent (replaced for most free and consumer accounts by Antigravity CLI in June 2026). Last checked 2026-11-10, against Gemini CLI’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.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 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 connect

3. 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_KEY

4. 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.js

A .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_KEY

5. 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 Gemini CLI

The instructions file

Put the note from step 5 in GEMINI.md in the project root, or AGENTS.md once you add it to the file names Gemini reads (Gemini CLI doesn’t read AGENTS.md by default):

{ "context": { "fileName": ["AGENTS.md", "GEMINI.md"] } }

Put that in ~/.gemini/settings.json. Run /memory show to check that the note is loaded.

Every project: ~/.gemini/GEMINI.md is loaded first, then the workspace’s files; all are combined. The note to put there: Use Vando in every project.

Approvals and the sandbox

Gemini CLI asks before each shell command. To let vando run through without its prompt (your phone still asks), add it to the allowed tools in ~/.gemini/settings.json:

{ "tools": { "allowed": ["run_shell_command(vando run)"] } }

Gemini’s docs show this form for git; check that it matches vando run before you rely on it. The sandbox is off unless you start with -s. On a Mac the default Seatbelt profile restricts writes and allows the network; whether it blocks the keychain or the vando key file isn’t documented, so run vando connect in your own terminal and test a sandboxed run. The Docker sandbox image has no vando in it and no access to your keychain or home folder.

MCP tools (optional)

Most work goes through vando run, which keeps secrets out of the chat. Add the tools only when Gemini CLI must read a value itself; a value a tool returns stays in the conversation (the tools). Add the server to ~/.gemini/settings.json (all projects) or .gemini/settings.json (this project), or gemini mcp add -s user vando vando mcp:

{ "mcpServers": { "vando": { "command": "vando", "args": ["mcp"] } } }

Run /mcp to see vando connected with its tools. Gemini removes variables named like *KEY* or *TOKEN* from the environment it passes to MCP servers. In a folder you haven’t marked trusted, MCP servers don’t connect.

Cloud and remote sessions

Cloud Shell and Cloud Workstations come with Gemini CLI installed, and you can install vando there with npm. A connect needs someone to read the code and enter it on the phone; a Cloud Shell has no keychain, so vando keeps its key in a file. The Gemini GitHub Action runs unattended; use Vando with Gemini CLI on a computer you sit at.

If something goes wrong

  • Google announced on 19 May 2026 that Gemini CLI is replaced by Antigravity CLI for free, Google AI Pro and Ultra accounts from 18 June 2026. Gemini CLI continues for Code Assist Standard and Enterprise licences and for paid API keys. Antigravity CLI isn’t covered here.
  • AGENTS.md isn’t read unless you add it to context.fileName.
  • A shell command is stopped after 300 seconds without output, so a phone wait is safe; print progress anyway.
  • If a command waits for input, the user has to focus the shell; vando doesn’t prompt under an agent.
  • Run vando doctor in your own terminal: it says what is wrong and the command that fixes it.
  • If a vando command stops, relay what it says; the line ends with a link to the errors reference.

Sources

What this page is written from:

Last verified , Gemini CLI’s own current documentation (links at the end)

On this page