# Connect Aider

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

Connect Aider 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 terminal pair programmer. Last checked 2026-11-10, against Aider’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 Aider

### The instructions file

Put the note from step 5 in Aider loads no rules file by itself. Put the note in `AGENTS.md` (or `CONVENTIONS.md`) and load it read-only: add `read: AGENTS.md` to `.aider.conf.yml` in the repository root, or start with `aider --read AGENTS.md`.

**Every project:** Aider has no user-level file; `read:` in a home-folder `~/.aider.conf.yml` can point at a file holding the note (files loaded last win). The note to put there: [Use Vando in every project](https://getvando.com/docs/connect-an-ai/every-project).

### Approvals and the sandbox

Aider has no sandbox and no allow list: its commands run as you, with your network, home folder and keychain. Aider asks `Run shell command?` before each command it suggests; answer **Y**. You can also run one yourself with `/run vando connect` or `/run vando run --secret NAME -- <command>`, and answer **N** to “Add command output to the chat?” for the connect code, so it isn’t sent to the model.

With `--yes-always`, Aider answers “no” to suggested shell commands, so an unattended Aider never runs `vando run`. That is a limit of Aider, not of Vando.

### MCP tools (optional)

Aider has no MCP support, so Vando’s MCP tools ([the tools](https://getvando.com/docs/reference/mcp)) aren’t available with it. Use `vando run`.

### Cloud and remote sessions

Aider has no hosted agent: it runs wherever you start it. Use Vando with Aider on a computer you sit at; in CI, `--yes-always` stops suggested commands.

### If something goes wrong

- Aider has no MCP support, so the MCP tools (`get_secret` and the rest) aren’t available with it; use `vando run`.
- Aider passes only a command’s output to the model, not its exit code, so the rules note should tell the model to read what `vando` prints and run the same command again when it says it is waiting for the phone.
- There is no automatic retry: you or the model must run the command again after exit 75.
- Keep Vando-managed secrets out of Aider’s `.env`: Aider loads it into its own environment, and every command it runs inherits it.
- 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:

- [Aider: conventions](https://aider.chat/docs/usage/conventions.html)
- [Aider: commands](https://aider.chat/docs/usage/commands.html)
- [Aider: options](https://aider.chat/docs/config/options.html)
- [Aider: install](https://aider.chat/docs/install.html)
