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.
JetBrains’ coding agent: the Junie CLI, the IDE plugin and the AI Assistant chat. Last checked 2026-11-10, against JetBrains Junie’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 JetBrains Junie
The instructions file
Put the note from step 5 in AGENTS.md in the project root. If the repository has .junie/AGENTS.md, Junie uses that file on its own and ignores the root one, so put the note in whichever file wins (~/.junie/AGENTS.md covers every project).
Every project: ~/.junie/AGENTS.md is included whenever it exists; project guidelines win where they conflict. The note to put there: Use Vando in every project.
Approvals and the sandbox
Junie’s CLI asks before most terminal commands. To skip its prompt for vando run (your phone still asks), add an entry to ~/.junie/allowlist.json:
{ "defaultBehavior": "ask", "rules": { "executables": { "rules": [ { "prefix": "vando run ", "action": "allow" } ] } } }Each part of a chained command must match, and multi-line commands always ask. In the IDE plugin the Action Allowlist takes terminal rules as Java regular expressions, for example ^\Qvando run --secret \E[^\s;&|<>@$]+ -- .*$. Junie’s sandbox (junie --sandbox, in its preview builds) leaves the network open but limits writes to the project, so vando connect will probably fail inside it: run it 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 JetBrains Junie must read a value itself; a value a tool returns stays in the conversation (the tools). Add the server to .junie/mcp/mcp.json (this project) or ~/.junie/mcp/mcp.json; the IDE’s Tools, Junie, MCP Settings page saves to the user file:
{ "mcpServers": { "vando": { "command": "vando", "args": ["mcp"], "timeout": 120000 } } }The default request timeout is one minute and covers tool calls; timeout is in milliseconds. In the CLI, /mcp lists the server. The IDE’s MCP allow rule covers all MCP tools; there are no per-server rules yet.
Cloud and remote sessions
Junie’s remote mode tunnels a session that is running on your computer, so commands still run there and Vando works as it does locally (the computer must stay awake). Junie’s GitHub Action runs unattended on a runner; use Vando with Junie on a computer you sit at.
If something goes wrong
- A
.junie/AGENTS.mdin the repository hides the rootAGENTS.mdand the note in it. - The one-minute MCP timeout is tight against a phone approval; set
timeoutto 120000. - Restart the IDE after installing
vando, so its terminal has the newPATH. - How long the CLI lets a command run isn’t documented.
- 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:
- Junie: guidelines and memory
- Junie: MCP configuration
- Junie: CLI allowlist
- Junie: IDE allowlist
- Junie: remote mode
Last verified , JetBrains Junie’s own current documentation (links at the end)
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.
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.