Connect Antigravity CLI
Connect Antigravity 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 terminal agent (agy), which replaced Gemini CLI for personal Google accounts in June 2026. Last checked 2026-11-10, against Antigravity 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.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 Antigravity CLI
The instructions file
Put the note from step 5 in AGENTS.md or GEMINI.md in the project root (it reads the workspace folder and each parent up to the repository root, not subfolders), or ~/.gemini/AGENTS.md for every project. Rule files under .agents/rules/ need frontmatter.
Every project: ~/.gemini/AGENTS.md is always on (Google’s rules page also lists ~/.gemini/GEMINI.md and the ~/.gemini/config/ forms); rules add up within a 20,000-token budget. The note to put there: Use Vando in every project.
Approvals and the sandbox
Antigravity CLI asks before every command by default. To let vando run through its own prompt (your phone still asks), add a rule to ~/.gemini/antigravity-cli/settings.json:
{ "permissions": { "allow": ["command(vando run)"] } }Rules match word by word, and a command containing $(...) turns prefix matching off. The sandbox is off by default and switches on with Auto mode or --sandbox: inside it there is no network and only the workspace and temp folders are writable, so vando run fails before it reaches the phone unless a rule allows it (an allowed command(...) rule runs outside the sandbox, per Google’s docs). Business and enterprise accounts use unsandboxed(...) rules instead. Google’s docs don’t say whether the keychain is reachable, 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 Antigravity CLI must read a value itself; a value a tool returns stays in the conversation (the tools). Add the server to ~/.gemini/config/mcp_config.json (all projects) or .agents/mcp_config.json (this project):
{ "mcpServers": { "vando": { "command": "vando", "args": ["mcp"] } } }Antigravity CLI ignores MCP servers still listed in the old Gemini CLI file ~/.gemini/settings.json: move them. A tool call times out after three minutes by default, well above a phone approval. /mcp shows the server’s status. The docs describe no agy mcp add command.
Cloud and remote sessions
Antigravity’s Remote Agents (AI Pro and Ultra personal accounts) run in a Google-managed environment that doesn’t support local MCP servers, so use Vando with the CLI on a computer you sit at. Remote Control drives your own computer, so vando should work through it.
If something goes wrong
- Without the allow rule you get Antigravity’s prompt and then the phone’s.
- In sandbox mode the command fails before it reaches the phone unless a rule allows it.
- Old Gemini CLI MCP entries and skills in
~/.gemini/settings.jsonand.gemini/skills/aren’t read; move them. - The docs give no shell-command timeout; forum posts report background commands stuck on “running”. Run
vando runin the foreground and run it again after exit 75. - 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:
Last verified , Antigravity CLI’s own current documentation (links at the end)
Connect JetBrains Junie
Connect JetBrains Junie 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.
Give one secret for a time
At the end, one command (yours or Claude’s) runs with one secret from your vault, for as long as you chose on your phone, and the secret never appears in Claude’s conversation.