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

The open-source coding agent for VS Code, JetBrains and the terminal. With Vando, your keys stay on your phone. When Cline 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 Cline guide, step by step

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

Set up Cline in four steps.

  1. 1 · Install vando and connect it to your phoneIn your own terminal, not through Cline. 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, or in a Cline-only rule file .clinerules/vando.md. In the Rules panel, check that the file is switched on.
  3. 3 · Let vando run reach your phoneCline has no fixed allow list for commands: you approve each one, or switch on “Execute safe commands” or “Execute all commands”. Cline’s documentation recommends approving each one. In Cline’s terminal agent, auto-approve is on by default, with no allow or deny list; leave vando run to the phone, which is the real gate. Nothing in Cline blocks the network or your keychain for local runs.
  4. 4 · The MCP tools, if you want themOptional. Add the server to ~/.cline/data/settings/cline_mcp_settings.json (CLINE_MCP_SETTINGS_PATH moves it); in the VS Code extension, open MCP Servers, then Configure; or run cline mcp add vando --yes -- vando mcp. Cline’s docs don’t name a timeout key for MCP; check the server’s settings in the MCP panel.
    {
      "mcpServers": {
        "vando": { "command": "vando", "args": ["mcp"], "disabled": false, "autoApprove": [] }
      }
    }

Use Vando in every project.

Cline reads ~/Documents/Cline/Rules in every project. A folder of markdown rule files that apply to every workspace (Cline also searches ~/.cline/rules and ~/Cline/Rules, and reads ~/.agents/AGENTS.md). Rules without frontmatter are always on and can be switched off in the Rules menu; workspace rules win where they conflict. (Cline’s rules docs.)

Put this note there, so Cline 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: A build that needs a registry token, from VS Code or JetBrains.

You
Ask Cline to build and publish the package.
Cline runs
vando run --secret NPM_TOKEN -- pnpm publish
Cline shows
Its approve button for the command (unless you turned on an execute mode), then “Waiting for your phone”.
Your phone shows
“Cline · MacBook wants to use NPM_TOKEN”. Give once; the publish runs with the token in its environment.

In the cloud, or on another computer.

Cline’s cloud agents don’t load rules or MCP servers (its docs say so), and each session runs in its own sandbox, so Vando isn’t usable there. Cline Desktop over SSH runs the agent on the remote computer: install and connect vando there.

Good to know with Cline.

Questions.

Should I turn on “Execute all commands” for Vando?

You don’t have to. Cline’s docs recommend approving each command; your phone is the gate for the secret either way. The terminal agent auto-approves by default, and the phone still asks.

Where is Cline’s MCP settings file?

~/.cline/data/settings/cline_mcp_settings.json, or the path in CLINE_MCP_SETTINGS_PATH. In VS Code, MCP Servers → Configure opens it; cline mcp add vando --yes -- vando mcp writes it for you.

Do Cline’s global rules reach every project?

Yes: markdown files in ~/Documents/Cline/Rules apply to every workspace, and workspace rules win where they conflict. Put the every-project note there and switch it on in the Rules menu.

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 →