# Vando

> Vando sits between a person (or an AI agent acting for them) and consequential actions. The person's phone holds the keys; laptops and AI agents ask the phone, and the person approves or denies there. Every answer is a signed receipt. Early access: the phone app runs on Android, and the `vando` command for Claude Code runs from a copy of the Vando code (no published package yet).

Start here if you are setting someone up: [Setup steps for an AI agent](https://getvando.com/docs/for-agents.md). Every page below is plain markdown.

## Get started

- [Overview](https://getvando.com/docs/index.md): Short pages on what Vando does, how to set it up, and where its limits are. Written for people, and for the AI agents they paste things into.
- [What Vando is](https://getvando.com/docs/start.md): Your phone holds the keys. Anything that wants to use one, your laptop or an AI, asks your phone first. You say yes or no.
- [Claude Code in 5 to 8 minutes](https://getvando.com/docs/quickstart/claude-code.md): At the end, Claude Code runs a command with one of your secrets after you tap Give on your phone, and its risky commands wait for your OK. The first time takes 5 to 8 minutes, with the Vando app already set up on your phone.
- [Your passwords in Vando](https://getvando.com/docs/quickstart/passwords.md): At the end, the Vando app on your Android phone holds your passwords, your recovery kit is on paper, and your phone fills your logins for you.

## Guides

- [Connect Claude Code](https://getvando.com/docs/connect-claude-code.md): Connect Claude Code on your computer to the Vando app on your phone. Then risky commands wait for your OK, and Claude asks you for a secret instead of reading it from a file. The first time takes about 5 to 8 minutes, with the app already on your phone.
- [Give one secret for a time](https://getvando.com/docs/guides/one-secret.md): At the end, one command (yours or Claude’s) runs with one secret from your vault, for as long as you chose on your phone, and the secret never appears in Claude’s conversation.
- [A whole project](https://getvando.com/docs/guides/project.md): At the end, a project’s .env files live in your vault as one folder per environment, and `vando run -- pnpm dev` gives the program everything it needs after one Give on your phone.
- [Bring passwords from another app](https://getvando.com/docs/guides/import.md): At the end, the passwords from your old password manager or browser are in your Vando vault, approved once with your fingerprint, and the export file is deleted.
- [A new phone](https://getvando.com/docs/guides/new-phone.md): At the end, your new phone opens your vault, and your old phone is cut off. With another phone of yours this takes a few minutes; with only your recovery kit, it takes 48 hours.
- [Your laptop and Chrome](https://getvando.com/docs/guides/laptop.md): At the end, the Vando extension in Chrome on your laptop fills and saves logins, and every fill is approved on your phone, unless you trust the laptop for the evening.
- [Your recovery kit](https://getvando.com/docs/recovery-kit.md): Your spare key, on paper. If every phone is lost, it gets you back in.

## Concepts

- [How approvals work](https://getvando.com/docs/approvals.md): When your laptop or an AI wants something, it asks your phone. You see exactly what it wants, and you say yes or no. Nothing happens until you do.
- [The four levels](https://getvando.com/docs/concepts/levels.md): What Easy, Just me, Two devices and Fort Knox each ask for, who they keep out, and how a thing’s level shapes everything else, from autofill to what a program can be given.
- [Vaults and folders](https://getvando.com/docs/concepts/vaults.md): How vaults, folders and tags sort your things, why where a thing lives never changes its lock, and what the Trash keeps.
- [Devices: who holds, who asks](https://getvando.com/docs/concepts/devices.md): Which of your devices hold the keys to your vault, which only ask, and what happens when you add a phone, add a security key or cut a device off.
- [Access windows and grants](https://getvando.com/docs/concepts/access-windows.md): The three kinds of access that last for a while instead of one ask at a time, who sets each one, how long it can run, and what ends it.

## Reference

- [CLI commands](https://getvando.com/docs/reference/cli.md): Every vando command, its flags and exit codes, made from the command itself.
- [MCP tools](https://getvando.com/docs/reference/mcp.md): The tools an AI gets from vando-mcp, word for word as the server describes them.
- [Errors and exit codes](https://getvando.com/docs/reference/errors.md): What each exit code means, and what the vando command says when something is wrong, word for word.
- [Glossary](https://getvando.com/docs/glossary.md): One definition per word, in the same words the app uses. Each term has its own link, so you can point someone straight at it.

## Trust

- [Security in plain words](https://getvando.com/docs/security.md): No system is unbreakable, and we won’t pretend ours is. This page says what protects you and, just as plainly, what we can’t promise.
- [What exists, what’s coming](https://getvando.com/docs/roadmap.md): Vando is built in three releases, named by who each is useful to. V1 Me, V2 Us, V3 Us + AI. We are in V1, in early access. This page says what works and what doesn’t, and we update it as things change.
- [Changelog](https://getvando.com/docs/changelog.md): What changed in Vando, newest first. Early access, so nothing here is in an app store yet.

## For AI agents

- [Setup steps as markdown](https://getvando.com/docs/for-agents.md)
- [llms.txt](https://getvando.com/docs/llms.txt)