# Use Vando in every project

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

One note in your AI tool's user-level instructions file, so it gets secrets through Vando in every project, suggests vando add in a new one, and suggests moving a project's .env files into Vando.

## The note

Most tools read a user-level instructions file that applies to every project. Put this note there, so the tool gets secrets through Vando everywhere, suggests `vando add` in a new project, and suggests `vando init` when it finds a project's `.env` files:

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

## Where it goes

| Tool | The file for every project |
| --- | --- |
| Claude Code | `~/.claude/CLAUDE.md` (and rules in `~/.claude/rules/`) |
| Codex | `~/.codex/AGENTS.md` |
| Cursor | none: User Rules in the settings (Customize → Rules) |
| Devin Desktop | `~/.devin/global_rules.md` |
| GitHub Copilot | `~/.copilot/copilot-instructions.md` (VS Code and the Copilot CLI) |
| Gemini CLI | `~/.gemini/GEMINI.md` |
| Aider | none: `read:` in `~/.aider.conf.yml` pointing at a file with the note |
| Cline | `~/Documents/Cline/Rules/` (a folder of rule files) |
| OpenCode | `~/.config/opencode/AGENTS.md` |
| Kiro | `~/.kiro/steering/` (a folder of steering files) |
| JetBrains Junie | `~/.junie/AGENTS.md` |
| Antigravity CLI | `~/.gemini/AGENTS.md` |

Each tool's page says how its file is read and what wins when a project file disagrees (checked against the tools' own docs, 2026-11-13): [Codex](https://getvando.com/docs/connect-an-ai/codex), [Cursor](https://getvando.com/docs/connect-an-ai/cursor), [Devin Desktop](https://getvando.com/docs/connect-an-ai/devin-desktop), [GitHub Copilot](https://getvando.com/docs/connect-an-ai/github-copilot), [Gemini CLI](https://getvando.com/docs/connect-an-ai/gemini-cli), [Aider](https://getvando.com/docs/connect-an-ai/aider), [Cline](https://getvando.com/docs/connect-an-ai/cline), [OpenCode](https://getvando.com/docs/connect-an-ai/opencode), [Kiro](https://getvando.com/docs/connect-an-ai/kiro), [JetBrains Junie](https://getvando.com/docs/connect-an-ai/junie), [Antigravity CLI](https://getvando.com/docs/connect-an-ai/antigravity-cli); Claude Code is [Connect an AI](https://getvando.com/docs/connect-an-ai). For Claude Code, `vando setup --global` writes this note into `~/.claude/CLAUDE.md` for you, between markers, and `vando setup --global --remove` takes it out again (from CLI 0.1.9). For the other tools, paste it yourself. `vando setup` on its own writes the per-project note only.
