Keep Kiro’s API keys out of .env files and chats.
AWS’s agentic IDE and command-line agent. With Vando, your keys stay on your phone. When Kiro 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.
Checked against Kiro’s own documentation on 2026-11-10; the guide links its sources.
Set up Kiro in four steps.
-
1 · Install vando and connect it to your phoneIn your own terminal, not through Kiro.
vando connectshows 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 · Tell it how to askPut the note in
AGENTS.mdin the project root (Kiro always includes it), or in a steering file in.kiro/steering/. -
3 · Let vando run reach your phoneWith no
permissions.yaml, Kiro prompts for every shell command beyond a short safe list. To letvando runthrough its prompt (your phone still asks), add a rule to~/.kiro/settings/permissions.yaml. Kiro’s local command sandbox is off by default; when it is on (and always with/autonomous on), outbound network is blocked, so add asandbox_networkrule for Vando’s server (the addressvandonames in its blocked message) to the same file.rules: - capability: shell match: ["vando run *"] effect: allow -
4 · The MCP tools, if you want themOptional. Add the server to
.kiro/settings/mcp.json(this project) or~/.kiro/settings/mcp.json; the IDE andkiro-clishare them. The IDE needs its MCP setting turned on; saving the file reconnects servers.mcpSandboxingis off by default and would cover the Vando server too.{ "mcpServers": { "vando": { "command": "vando", "args": ["mcp"], "disabled": false } } }
Use Vando in every project.
Kiro reads ~/.kiro/steering/ in every project. A folder of markdown steering files that apply to all workspaces; files with the default always inclusion load on every interaction, and AGENTS.md there is always included. Workspace steering wins where they conflict. (Kiro’s steering docs.)
Put this note there, so Kiro 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: Syncing a build to S3 with your AWS keys.
- You
- Ask Kiro to publish the site build.
- Kiro runs
vando run --secret AWS_ACCESS_KEY_ID --secret AWS_SECRET_ACCESS_KEY -- aws s3 sync dist s3://my-site- Kiro shows
- No prompt with the shell rule above, then “Waiting for your phone”.
- Your phone shows
- “Kiro · MacBook wants to use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY”. Give once; the AWS CLI gets both in its environment and the sync runs.
In the cloud, or on another computer.
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.
Good to know with Kiro.
- Restart Kiro after installing
vandosoPATHincludes it. - For
kiro-cliMCP servers, export any variables before starting it: project.envfiles aren’t loaded. - Headless runs need
KIRO_API_KEYand can’t read a connect code, so connect first in your own terminal. - Kiro’s docs don’t say whether a sandboxed command can reach the macOS keychain or your home folder, so run
vando connectin your own terminal.
Questions.
Why does Kiro block vando run when I turn the sandbox on?
With the sandbox on, and always in /autonomous on, outbound network is blocked. Add a sandbox_network rule for Vando’s server to ~/.kiro/settings/permissions.yaml; vando names the address in its blocked message.
Do steering files reach every project?
Yes: markdown files in ~/.kiro/steering/ with the default always mode load on every interaction in every workspace, and workspace steering wins where they conflict. Put the every-project note there.
Can Kiro’s cloud sessions use Vando?
Not well: they ignore ~/.kiro/ and permissions.yaml, approve actions by default, and each sandbox would need its own connect. Keep Vando for the Kiro IDE and kiro-cli on a computer you sit at.
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 →