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

JetBrains’ coding agent: the Junie CLI, the IDE plugin and the AI Assistant chat. With Vando, your keys stay on your phone. When JetBrains Junie 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.

The JetBrains Junie guide, step by step

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

Set up JetBrains Junie in four steps.

  1. 1 · Install vando and connect it to your phoneIn your own terminal, not through JetBrains Junie. 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 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.
  3. 3 · Let vando run reach your phoneJunie’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. 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 run vando connect in your own terminal.
    { "defaultBehavior": "ask", "rules": { "executables": { "rules": [ { "prefix": "vando run ", "action": "allow" } ] } } }
  4. 4 · The MCP tools, if you want themOptional. 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. The default request timeout is one minute and covers tool calls, tight against a phone approval, so set timeout (milliseconds) to 120000. In the CLI, /mcp lists the server.
    { "mcpServers": { "vando": { "command": "vando", "args": ["mcp"], "timeout": 120000 } } }

Use Vando in every project.

JetBrains Junie reads ~/.junie/AGENTS.md in every project. Included whenever it exists (%USERPROFILE%\.junie\AGENTS.md on Windows). Project guidelines are included as well and win where they conflict; identical lines are deduplicated. (Junie’s guidelines and memory docs.)

Put this note there, so JetBrains Junie 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: Publishing a library with a repository token, from the IDE.

You
Ask Junie to publish the release.
Junie runs
vando run --secret MAVEN_TOKEN -- ./gradlew publish
Junie shows
No prompt if the allowlist prefix matches, then “Waiting for your phone”.
Your phone shows
“JetBrains Junie · MacBook wants to use MAVEN_TOKEN”. Give once; Gradle gets the token in its environment and publishes.

In the cloud, or on another computer.

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.

Good to know with JetBrains Junie.

Questions.

Junie ignores my AGENTS.md note. Why?

If the repository has .junie/AGENTS.md, Junie uses that file and ignores the root AGENTS.md. Put the note in whichever file wins, or in ~/.junie/AGENTS.md for every project.

Why set the MCP timeout to 120000?

Junie’s default request timeout is one minute and covers tool calls. A phone approval can take longer, so the Vando server entry sets timeout (in milliseconds) to two minutes.

Does Junie’s remote mode work with Vando?

Yes: remote mode tunnels a session running on your own computer, so commands and vando run there as usual, as long as the computer stays awake. The GitHub Action runs unattended and is not a fit.

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 →