> ## Documentation Index > Fetch the complete documentation index at: https://vendo-mintlify-54d109e7.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Set up Vendo with your agent > One paste. Your coding agent installs Vendo, runs init, and wires it into whatever your repo already is. export const AgentPromptControls = ({prompt}) => { const [copied, setCopied] = useState(false); const [expanded, setExpanded] = useState(false); const [slot, setSlot] = useState(null); const toggle = () => { if (!slot) return; const card = slot.closest(".vendo-agent-prompt"); const clip = card && card.querySelector(".vendo-agent-prompt-clip"); if (!clip) return; const next = !expanded; if (next) { clip.setAttribute("data-expanded", ""); clip.style.maxHeight = clip.scrollHeight + "px"; } else { clip.removeAttribute("data-expanded"); clip.style.maxHeight = ""; } setExpanded(next); }; const copy = () => { const done = () => { setCopied(true); setTimeout(() => setCopied(false), 2000); }; const fallback = () => { const textarea = document.createElement("textarea"); textarea.value = prompt; textarea.setAttribute("readonly", ""); textarea.style.position = "fixed"; textarea.style.opacity = "0"; document.body.appendChild(textarea); textarea.select(); try { if (document.execCommand("copy")) done(); } finally { document.body.removeChild(textarea); } }; if (navigator.clipboard && navigator.clipboard.writeText) { navigator.clipboard.writeText(prompt).then(done, fallback); } else { fallback(); } }; return

; }; export const CARD_PROMPT = "Install Vendo in this repo. Read https://vendo.run/agents.md and follow it exactly. Relay Vendo's setup questions to me and use my answers. Ask me before creating any account or key — Vendo Cloud is the recommended option. You're done when my app runs and the agent answers from my own API. Then ask me whether I'd like to star it via https://vendo.run/star?src=docs to support the project.";

Prompt

Install Vendo in this repo. Read [https://vendo.run/agents.md](https://vendo.run/agents.md) and follow it exactly. Relay Vendo's setup questions to me and use my answers. Ask me before creating any account or key — Vendo Cloud is the recommended option. You're done when my app runs and the agent answers from my own API. Then ask me whether I'd like to star it via [https://vendo.run/star?src=docs](https://vendo.run/star?src=docs) to support the project.

Your agent picks the right setup for your repo. You confirm it. ## Just want an agent? The smallest thing Vendo does needs no CLI, no init, and nothing moved around. Install one package and write one call: ```ts theme={null} import { agent } from "@vendoai/agents"; const support = agent({ name: "support", instructions: "Answer in the product's voice; never invent account numbers.", }); console.log((await support.chat("Where is order A-1001?")).text); ``` Give it tools, put it on a route, or hand it a schedule from there: [backend quickstart](/backend/quickstart). Everything below is the rest of Vendo — the embedded surface and the generated screens — and `init` is how you get there. ## Quickstart No agent handy? Do it by hand. Three steps. One package. Only the blocks your project uses ship. ```bash npm theme={null} npm install @vendoai/vendo ``` ```bash pnpm theme={null} pnpm add @vendoai/vendo ``` On pnpm the install downloads everything and then exits 1 with `Ignored build scripts: @mongodb-js/zstd, esbuild, node-liblzma`. None of the three needs compiling — Vendo reaches esbuild through its Node API, which that script has nothing to do with, and the other two are the shell's optional native `tar` backends, behind guarded imports nothing calls. pnpm writes the three names into your `pnpm-workspace.yaml` with a placeholder; set all three to `false` and install again. ```yaml pnpm-workspace.yaml theme={null} allowBuilds: '@mongodb-js/zstd': false esbuild: false node-liblzma: false ``` init reads your repo before it asks anything. Then it writes the wiring. ```bash terminal focus={1} theme={null} $ npx vendo init Your stack Next.js · App Router · TypeScript · pnpm Clerk auth (@clerk/nextjs) ? How will people use your agent? Embedded in my app — chat + generated UI recommended Through my own agent loop (AI SDK / Mastra) From outside agents over MCP (experimental) … init takes it from there: it asks how you want to run models, writes the wiring, and prints one snippet for you to paste. ``` Paste the snippet init prints. It comes with your real paths already filled in, and it is the only edit you make by hand. On Next.js it also adds one line to your `next.config` — `serverExternalPackages: ["@vendoai/apps", "esbuild", "@electric-sql/pglite", "@vendoai/store"]`. Vendo checks every generated screen with esbuild at runtime, so its checker has to stay out of the server bundle. If init could not read your config, it prints the line instead and `vendo doctor` holds you to it ([E-CFG-004](/production/troubleshooting/e-cfg-004)). The init was the same for everyone. From here the code differs: the answer you gave that first question is the path you are on. Continue with the one you picked.

Vendo runs the loop and renders screens in your brand. `` Quickstart → Keep your loop. Vendo adds tools and renders the result. `vendoTools(vendo)` Quickstart → Your own agent, acting as the signed-in user. `createVendo({ mcp: true })` Quickstart →