Keep Gemini CLI’s API keys out of .env files and chats.

Google’s command-line coding agent, now for Code Assist Standard and Enterprise licences and paid API keys. Personal Google accounts moved to Antigravity CLI in June 2026. With Vando, your keys stay on your phone. When Gemini CLI 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.

On a personal Google account (free, AI Pro or Ultra), Google replaced Gemini CLI with Antigravity CLI on 18 June 2026. Vando for Antigravity CLI →

The Gemini CLI guide, step by step

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

Set up Gemini CLI in four steps.

  1. 1 · Install vando and connect it to your phoneIn your own terminal, not through Gemini CLI. 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 GEMINI.md in the project root. Gemini CLI doesn’t read AGENTS.md unless you add it to the file names it reads, in ~/.gemini/settings.json; /memory show checks the note is loaded.
    { "context": { "fileName": ["AGENTS.md", "GEMINI.md"] } }
  3. 3 · Let vando run reach your phoneGemini 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. Gemini’s docs show this form for git; check 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 allows the network but whether it reaches the keychain isn’t documented, and the Docker image has no vando and no access to your home folder.
    { "tools": { "allowed": ["run_shell_command(vando run)"] } }
  4. 4 · The MCP tools, if you want themOptional. Add the server to ~/.gemini/settings.json (all projects) or .gemini/settings.json (this project), or run gemini mcp add -s user vando vando mcp; /mcp shows it connected. Gemini removes variables named like *KEY* or *TOKEN* from the environment it passes to MCP servers, and in a folder you haven’t marked trusted, MCP servers don’t connect.
    { "mcpServers": { "vando": { "command": "vando", "args": ["mcp"] } } }

Use Vando in every project.

Gemini CLI reads ~/.gemini/GEMINI.md in every project. Loaded first, then the workspace’s GEMINI.md files; all are combined and sent with every prompt. context.fileName can add AGENTS.md to the names it reads. (Gemini CLI’s GEMINI.md docs.)

Put this note there, so Gemini CLI 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: Deploying a Cloud Run service with a service key.

You
Ask Gemini CLI to deploy the service.
Gemini CLI runs
vando run --secret GCP_SA_KEY -- gcloud run deploy api --source .
Gemini CLI shows
No prompt if the allowed-tools rule matches, then “Waiting for your phone”.
Your phone shows
“Gemini CLI · MacBook wants to use GCP_SA_KEY”. Give once; gcloud gets the key in its environment and the deploy runs.

In the cloud, or on another computer.

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.

Good to know with Gemini CLI.

Questions.

Is Gemini CLI still the right page for me?

If you use Gemini CLI with a Code Assist Standard or Enterprise licence or a paid API key, yes. On a personal Google account Google replaced it with Antigravity CLI in June 2026, which has its own page.

Why doesn’t Gemini read my AGENTS.md note?

Gemini CLI reads GEMINI.md by default. Add AGENTS.md to context.fileName in ~/.gemini/settings.json, then check with /memory show.

Why does the Vando MCP server see no KEY variables?

Gemini strips variables named like *KEY* or *TOKEN* from the environment it passes to MCP servers. Vando’s server needs none of them: it talks to your phone, and the secrets arrive locked to this computer’s own key.

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 →