# Connect Cline

URL: https://getvando.com/docs/connect-an-ai/cline

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

The open-source coding agent for VS Code, JetBrains and the terminal. Last checked 2026-11-10, against Cline’s own documentation (the links at the end). If a step doesn’t match what you see, [tell us](https://getvando.com/support). For Claude Code, [Connect an AI](https://getvando.com/docs/connect-an-ai) is the same road.

## The steps every tool shares

**1.** Install `vando` in your own terminal (not through your AI tool):

```bash
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:

```bash
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.

```bash
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.

```bash
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`.

```bash
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:

```text
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):

```md
## 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 Cline

### The instructions file

Put the note from step 5 in `AGENTS.md` in the project root, or a Cline-only rule file `.clinerules/vando.md`. In the Rules panel, check that the file is switched on.

**Every project:** `~/Documents/Cline/Rules/` holds rule files for every workspace (Cline also searches `~/.cline/rules` and `~/.agents/AGENTS.md`); workspace rules win where they conflict. The note to put there: [Use Vando in every project](https://getvando.com/docs/connect-an-ai/every-project).

### Approvals and the sandbox

Cline 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**, and it has 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.

### MCP tools (optional)

Most work goes through `vando run`, which keeps secrets out of the chat. Add the tools only when Cline must read a value itself; a value a tool returns stays in the conversation ([the tools](https://getvando.com/docs/reference/mcp)). Add the server to `~/.cline/data/settings/cline_mcp_settings.json` (set `CLINE_MCP_SETTINGS_PATH` to move it); in the VS Code extension, open MCP Servers, then Configure; or `cline mcp add vando --yes -- vando mcp`:

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

Cline’s docs don’t name a timeout key for MCP; check the server’s settings in the MCP panel.

### Cloud and remote sessions

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.

### If something goes wrong

- Restart VS Code after installing `vando`, or Cline’s terminal may not find it on `PATH`.
- Cline’s docs say little about how it runs commands and passes the environment; if `vando` is not found, use its full path.
- The terminal agent approves commands by default; a phone approval still protects every secret.
- 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](https://getvando.com/docs/reference/errors).

## Sources

What this page is written from:

- [Cline: rules](https://docs.cline.bot/customization/cline-rules)
- [Cline: MCP](https://docs.cline.bot/mcp/mcp-overview)
- [Cline: auto-approve](https://docs.cline.bot/features/auto-approve)
- [Cline: CLI overview](https://docs.cline.bot/usage/cli-overview)
- [Cline: cloud agents](https://docs.cline.bot/usage/cloud-agents)
