VandoVandoDocs
Connect your AI tool

Connect Kiro

Connect Kiro 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.

AWS’s agentic IDE and command-line agent. Last checked 2026-11-10, against Kiro’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 Kiro

The instructions file

Put the note from step 5 in AGENTS.md in the project root (Kiro always includes it), or a steering file in .kiro/steering/.

Every project: ~/.kiro/steering/ holds steering files for all workspaces (the default always mode loads on every interaction); workspace steering wins. The note to put there: Use Vando in every project.

Approvals and the sandbox

With no permissions.yaml, Kiro prompts for every shell command beyond a short safe list. To let vando run through its prompt (your phone still asks), add to ~/.kiro/settings/permissions.yaml:

rules:
  - capability: shell
    match: ["vando run *"]
    effect: allow

Kiro’s local command sandbox is off by default. When it is on (and always with /autonomous on), outbound network is blocked, so add a sandbox_network rule for Vando’s server (the address vando names in its blocked message) to the same file. Kiro’s docs don’t say whether a sandboxed command can reach the macOS keychain or your home folder, 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 Kiro must read a value itself; a value a tool returns stays in the conversation (the tools). Add the server to .kiro/settings/mcp.json (this project) or ~/.kiro/settings/mcp.json; the IDE and kiro-cli share them:

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

The IDE needs its MCP setting turned on; saving the file reconnects servers. mcpSandboxing is off by default; if you turn it on, it covers the Vando MCP server too.

Cloud and remote sessions

Kiro’s cloud sessions (web and mobile) clone your repository into a managed sandbox that ignores ~/.kiro/ and permissions.yaml, and approves actions by default. Vando would need its own connect inside each sandbox. Use Vando with the Kiro IDE or kiro-cli on a computer you sit at.

If something goes wrong

  • Restart Kiro after installing vando so PATH includes it.
  • For kiro-cli MCP servers, export any variables before starting it: project .env files aren’t loaded.
  • Headless runs need KIRO_API_KEY; they can’t read a connect code, so connect first in your own terminal.
  • 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 , Kiro’s own current documentation (links at the end)

On this page