Your personal memory, across sessions, agents, and devices.

What Is v0 by Vercel? How the AI App Builder Works

memU Team memU Team

v0 by Vercel is an AI app builder. You describe an app in a chat. v0 writes the code, shows a live preview and deploys it to Vercel. It started in October 2023 as a UI generator. Since August 2025 it lives at v0.app and works as an agent that builds full-stack apps. Below is how v0 works in October 2026 and what it costs. We also look at what it keeps between chats, which decides how much you end up repeating.

What is v0, in one sentence?

v0 is a chat-based agent from Vercel that turns natural-language prompts into working Next.js apps you can deploy to Vercel in one click.

Vercel's docs call it "an AI agent that helps anyone create real code and full-stack apps and agents." The docs list product managers and designers next to engineers.

Vercel announced v0 on October 11, 2023, as "Generative UI." It generated React code with Tailwind CSS and shadcn/ui that you copied into your own app. Vercel said 100,000 people joined the waitlist in three weeks. On August 11, 2025, v0.dev became v0.app. Vercel described the new v0 as an agent that plans its work and checks it for errors.

How does v0 differ from a coding agent in your editor?

The closest alternative for most developers is a coding agent such as Claude Code or Cursor working on a repo you already have. Both write code from prompts. v0 starts in Vercel's sandbox with a fixed stack, and an editor agent starts from your repo.

v0 Coding agent in your editor
Where it runs Vercel's cloud, one sandbox per chat Your machine or the agent's cloud workspace
Default stack Next.js, React, TypeScript, Tailwind CSS, shadcn/ui Whatever your repo uses
Preview Live preview in the browser, preview deployment per branch Your own dev server
Deploy One click to Vercel Your existing pipeline
Reusable context Account Instructions, design system skills, project settings Instruction files such as CLAUDE.md or AGENTS.md, plus the host's own memory
Who it is for Anyone, including non-developers Mostly developers

Stack details come from the v0 FAQ. Preview and deploy details come from the GitHub and sandbox docs.

Vercel also publishes comparisons with competitors, such as v0 vs Bolt. Read those as vendor pages. They are useful for feature names and weak as a neutral verdict.

How does v0 work?

A VM-backed chat gets its own isolated virtual machine on Vercel Sandbox. The sandbox docs say it runs a full Node.js environment. v0 detects Next.js or Vite projects and starts the dev server for you. You can run commands through v0's Bash tool or a terminal tab. Files persist between sessions of the same chat. A sandbox starts with a 30-minute timeout and never lives more than 24 hours. If it has expired when you return, v0 recreates it.

Chats group into Projects. The projects docs describe a project as "one, cohesive app that many chats can contribute to." Chats in a project share the deployment and the encrypted environment variables. Deploying from any chat updates the same production URL.

Connecting GitHub keeps every v0 change reviewable. Once you connect a repository, it becomes the source of truth for the project's code. v0 pushes to a separate working branch, and each branch gets its own preview deployment. Publishing opens a pull request or reuses the existing one. If branch protection requires reviews or checks, v0 leaves the PR open for a human.

For teams that want v0 inside their own product, Vercel offers the v0 Platform API. It exposes the same app-building agent, including previews and deployment.

What does v0 cost?

v0 bills in credits that work like a prepaid balance. The pricing docs list these plans in October 2026:

Plan Price Monthly credits
Free $0 $5 once for new users
Plus $30 per user per month $30 per user
Business $100 per user per month $30 per user
Enterprise Custom Custom

The older Premium plan at $20 a month is closed to new users. Unused monthly credits roll over and expire after 65 days. Credits you buy separately expire one year after purchase.

Credits are spent on tokens, and the rate depends on the model you pick. For long projects, note what Vercel's pricing page counts as input: chat history and source files, next to your prompt. A long chat on a large codebase costs more per message than a fresh one.

What does v0 remember between chats?

v0 keeps context in four places, each with its own scope.

  1. The chat itself. History and files stay with the chat. The sandbox docs say a chat's files and processes "never cross from one chat to another."
  2. Instructions. These are reusable prompts saved to your account and applied when you check them. Two presets ship with v0: Be Concise and Plan Mode. Plan Mode makes v0 propose a plan and wait for approval. Custom ones, such as "design mobile first," are available in all your chats and projects.
  3. Project settings. Every chat in a project shares its environment variables and GitHub connection.
  4. Design systems. With Design Systems 2.0, you import your component package along with repos or Figma frames. v0 builds a starter app and waits for your approval. It then saves the result "as a skill" for your team or personal workspace. New chats start from that starter app. Existing projects do not update when the skill changes.

Everything else is gone when you open a new chat. That includes why a layout was rejected and the bug that took an hour to find. You have to carry it over yourself.

What should you read in the fine print?

Most claims about v0's quality come from Vercel. The agentic features in the August 2025 post are described by Vercel and illustrated with its own examples. We found no independent benchmark of v0 output in the sources we checked.

The FAQ is direct on two points. Vercel does not own the code v0 generates. It also warns that outputs may contain bugs or resemble other users' work. On data, v0 may use your prompts to improve its products. Enterprise customers and teams that opt out in Vercel settings are excluded from training.

v0 is strongest when your app is Next.js on Vercel. Other stacks can work from an imported repo, but the docs and templates assume that default.

The bottom line

Use v0 when you want a working Next.js prototype or internal tool deployed today, especially if a non-developer is driving. Connect GitHub early so every change lands as a reviewable pull request. If you have a design system, import it as a skill before the first real project. Decisions that should outlive a chat need to become an Instruction or a design system update. v0 keeps nothing else.

How do you keep project decisions when you move from v0 to a coding agent?

Many v0 projects follow the same path. A prototype starts in v0. The repo moves to GitHub, and the work continues in a coding agent such as Claude Code. The code survives that move. The reasoning stays behind in v0 chat history: which components were ruled out, which conventions the team agreed on. The next agent then has to relearn it from the code or from you. The same thing happens between two coding agents that each keep their own memory.

memU keeps that knowledge as a shared wiki of readable Markdown files. A scheduled background task slices new session logs from each supported host into jobs. The agent decides what is worth keeping and writes it as memory or skill Markdown. memU's own memory service makes no LLM calls. It stores what the agent wrote and retrieves it on request.

A standing instruction in CLAUDE.md or AGENTS.md tells the agent to retrieve before answering. All hosts share one backend, so a convention Codex learned is there when you switch to Claude Code. memU does not connect to v0 itself. It covers the coding agents you use once the repo leaves v0. To bring v0 decisions along, paste them into a session. The agent then records them.

To try the hosted version, which is free and syncs across devices, get an API key from memu.so and send your agent one message:

Read https://memu.pro/SKILL.md, follow its instructions to install and configure memU, API Key is YOUR_MEMU_API_KEY.

Self-hosting and the list of supported agents are in the memU GitHub repository. For why memU leaves the judgment to the agent, see memU gives memory back to the agent.

FAQ

Is v0 free?

There is a Free plan. New users get $5 in credits once, according to Vercel's pricing docs. Paid plans start at $30 per user per month for Plus, with $30 in monthly credits.

Is v0.dev the same as v0.app?

Yes. Vercel moved v0 from v0.dev to v0.app on August 11, 2025, when it relaunched v0 as an agent.

What framework does v0 use?

Per its FAQ, v0 builds with Next.js and React by default, styled with Tailwind CSS and shadcn/ui. It can also work from an imported GitHub repository.

Does v0 remember previous chats?

Not automatically. History and files stay inside each chat. Account Instructions and design system skills apply to every chat. Project settings apply only within one project.

Who owns code generated by v0?

You do. Vercel's FAQ says it does not own code generated from your prompts. It also says you are responsible for checking that code before commercial use.