Skip to main content
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.
Your agent picks the right setup for your repo. You confirm it.

Quickstart

No agent handy? Do it by hand. Three steps.
1

Install

One package, installed in the app you already have, on Node 20 or newer: the library your app imports, and the vendo CLI that wires it up ride together. Only the blocks your project uses ship.
On pnpm the install downloads everything, 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, 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.
pnpm-workspace.yaml
2

Run npx vendo init

init reads your repo before it asks anything, asks how people will use your agent, and writes the wiring. It ends with the list of files it touched and a link to the quickstart for the path you chose.
3

Continue in your direction

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.
direction-product

Vendo's Full-Stack Agent

Vendo runs the loop and renders screens in your brand.<VendoProvider>Quickstart →
direction-existing-agent

In your existing agent

Keep your loop. Vendo adds tools and renders the result.vendoTools(vendo)Quickstart →
direction-outside-agents

From outside agents

Your own agent, acting as the signed-in user.createVendo({ mcp: true })Quickstart →