Most coding assistants are a chat window bolted onto an editor. They can see your file and nothing else. They do not know what your backend is, which collections exist, or how your authentication works — so the code they write compiles, and then fails the moment it meets your data.
Vibe Agent starts from the other end. It is one panel of Vibe Studio, beside the files, the terminal and the live preview, looking at the same project you are — inside an environment that already has your platform in it.
It already knows what you are building on
The agent introspects the running platform rather than guessing at it. It can read the collections you have defined, the fields on them, the permissions attached and the services exposed to it. When it writes a query, it writes against a schema it has actually read.
That is the practical difference. Ask for a page listing this month's unpaid invoices and it does not invent an endpoint — it finds the one that exists.
Where it lives
Vibe Studio is the environment: a browser workspace with your files, a real terminal, a preview, and a dev environment that is already running. Vibe Agent is the panel inside it doing the work.
- Files — the project, editable by hand at any point
- Terminal — a real shell, not a simulated one
- Preview — the app running as you change it
- Agent — reads the project and the platform, then edits both
Nothing is generated into a void you then have to wire up. The workspace it edits is the workspace that runs.
Not tied to one model vendor
The agent is not built around a single provider. Model choice is a configuration concern rather than an architectural one, so the environment outlives whichever model is currently best at writing code.
Working with it
- Open the workspace — the dev environment is already up
- Describe the change in plain English, at whatever altitude suits you
- Watch it edit real files while the preview reloads
- Correct it in the editor or in the next instruction — both stick
- Deploy when it is doing what you wanted
The useful prompts are the specific ones. "Build me an app" produces something generic. "Add a deposit to the booking flow, charge 20% at reservation, refund it if they cancel more than 48 hours out" produces something you can ship, because every noun in it maps to something the platform already has.
Where this fits
Vibe Agent is for the part of the work that is genuinely yours — the screens, the flows, the rules of your business. The parts underneath, that every application needs and that are dangerous to guess at, are already built and already running: identity, permissions, files, payments, audit.
You are not asking an agent to invent a backend. You are asking it to build on one.
- Vibe Agent — what it is and where it runs
- Vibe Studio docs — the environment around it