← Coding

v0v0

VercelVercel

海外Outside China 免费+付费Free + paid WebWeb Next.jsNext.js VercelVercel 沙箱Sandbox MCPMCP GitHub同步GitHub sync 预装agentPreinstalled agents partial lifecycle: active 核验Checked 2026-10-22

v0 是 Vercel 的提示词到全栈应用平台：聊天生成 Next.js 应用，VM 沙箱内跑真终端与预装 agent （claude 可直接用），GitHub 同步进你的仓库，publish 走 Vercel 部署链——权限三档 Ask/Auto/Full，自定义模型是 Enterprise 面。

v0 is Vercel's prompt-to-full-stack platform: chats generate Next.js apps, a VM sandbox runs a real terminal with pre-installed agents (claude is ready to use), GitHub sync moves code into your repo, and publishing runs through the Vercel deployment chain — Ask/Auto/Full permission tiers, custom models are Enterprise-side.

适合与不适合When to use it, when not to

适合：Next.js/Vercel 栈团队、要沙箱终端与预装 agent、企业席位并入 Vercel 账号体系。不适合：栈不在 Vercel 生态、非 Enterprise 要自定义模型。

Fits: Next.js/Vercel-stack teams (the deployment chain is natively wired), wanting a real terminal and pre-installed agents in a sandbox, enterprise seats unified with the Vercel account system. Not a fit: stacks outside the Next.js/Vercel ecosystem (the deployment chain is part of the product semantics); non-Enterprise teams wanting custom models.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-22

出品属地Origin: 国外出品foreign-made　Vercel（美国）。Vercel (US).
国内使用Direct access: 大陆可直连direct OK　v0.app / v0.dev（307→v0.app）/ v0.dev/docs 大陆直连实测 200（2026-10-22）。v0.app / v0.dev (307 to v0.app) / v0.dev/docs measured 200 direct from mainland (2026-10-22).
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-22 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-22); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 官方「Choosing models」页：聊天内模型选择器选 v0 模型或从 AI Gateway 目录加自定义模型；更新版选择器与自定义模型面向 Enterprise 团队（自定义模型需团队 owner 批准）。会话内模型跟随最近一次响应，直到你换。应用内 AI 功能另有 ai-models 集成页（Grok/fal/Deep Infra 等）。
Official "Choosing models" page: pick the v0 model in the in-chat model picker, or add custom models from the AI Gateway catalog. The updated picker and custom models target Enterprise teams (custom models need team-owner approval). The model in a session follows the most recent response until you switch. In-app AI features have a separate ai-models integration page (Grok/fal/Deep Infra etc.).
运行位置Where it runs: 网页形态（v0.app）；VM-backed 聊天跑在 Vercel Sandbox 隔离虚拟机里（官方 sandbox 页：托管项目文件/跑预览/执行命令，聊天间状态互不泄漏；取代旧的浏览器内环境）。沙箱内预装编码 agent（官方页：终端里直接跑 claude 等 CLI，与 v0 内置助手同项目并用）。
Web form (v0.app); VM-backed chats run in isolated VMs on Vercel Sandbox (official sandbox page: hosts project files / runs previews / executes commands; state does not leak between chats; it replaces the older in-browser environment). Coding agents are pre-installed in the sandbox (official page: run CLIs like claude directly in the terminal, alongside v0's built-in assistant in the same project).
本地文件Local files: 项目在 v0 平台；GitHub 集成官方成页：代码进你的仓库、分支隔离、PR 与 CI 走标准流；可导入现有 GitHub 仓库（git-import 页）。官方明示 GitHub sync 只搬代码，不等于授予经 GitHub 部署的权限（部署权限看 Vercel 角色）。
Projects live on the v0 platform. The GitHub integration is an official page: code goes into your repositories, branch isolation, PRs and CI follow the standard flow; existing GitHub repositories can be imported (git-import page). The official states explicitly that GitHub sync only moves code — it does not grant deployment permission via GitHub (deployment permission follows Vercel roles).
关机后的任务Tasks after shutdown: 部署线常驻：preview 部署按分支构建、publish 更新 Vercel 生产部署（官方 deployments 页）；部署报错可「Fix with v0」读日志诊断修复（agentic-features 页）。构建任务关闭页面后是否续跑未核验到官方声明。
The deployment line is persistent: preview deployments build per branch, publish updates the Vercel production deployment (official deployments page); deployment errors can be diagnosed and fixed via "Fix with v0" reading the logs (agentic-features page). Whether build tasks keep running after the page is closed: not verified to an official statement.
工具与扩展Tools & extensions: agent 能力官方成页：web 搜索、浏览器使用、终端命令、错误修复、外部工具集成，全部在沙箱内； MCP 两条线（自带 MCP 服务器含预设清单/Marketplace 集成的 Remote MCP）；数据库集成 Supabase/Blob/Neon/Upstash；Figma 导入；v0 自身也可作为 MCP server 被别的 agent 调。
Agent capabilities are official pages: web search, browser use, terminal commands, error fixing, external tool integration — all inside the sandbox. Two MCP lines (bring-your-own MCP servers with a preset list / Remote MCP via Marketplace integrations). Database integrations: Supabase/Blob/Neon/Upstash; Figma import; v0 itself can also act as an MCP server called by other agents.
上下文与记忆Context & memory: 代码查看器（浏览/编辑代码、评审改动、加注释作下轮上下文）；Design mode 可视化选元素改样式回写代码；项目（projects）组织多聊天。跨会话记忆机制未核验到官方声明。
The code viewer (browse/edit code, review changes, add comments as next-round context); Design mode visually selects elements, edits styles and writes back to code; projects organize multiple chats. Cross-session memory: not verified to an official statement.
权限与限制Permissions & limits: 工具调用三档权限模式（Ask/Auto/Full）+ Agent Permissions 规则（MCP 页与 agentic-features 页口径）；企业面走 Vercel Enterprise：席位/v0 角色（Builder 等）与 Vercel 团队角色分离管理（enterprise 页）；安全页官方口径：不信任 LLM 生成代码——执行前安全分析、沙箱隔离、输入校验、对抗测试。
Tool-call permissions have three modes (Ask/Auto/Full) + Agent Permissions rules (MCP page and agentic-features page framing). The enterprise side goes through Vercel Enterprise: seats/v0 roles (Builder etc.) and Vercel team roles are managed separately (enterprise page). Security page official framing: do not trust LLM-generated code — security analysis before execution, sandbox isolation, input validation, adversarial testing.
适合什么任务Best for: 适合：Next.js/Vercel 栈团队（部署链原生打通）、要沙箱内跑真终端与预装 agent、企业席位与 Vercel 账号体系统一。不适合：栈不在 Next.js/Vercel 生态（部署线是产品语义一部分）、非 Enterprise 要自定义模型。
Good fit: Next.js/Vercel-stack teams (the deployment chain is natively connected), wanting real terminals and pre-installed agents inside a sandbox, unifying enterprise seats with the Vercel account system.

Not a fit: stacks outside the Next.js/Vercel ecosystem (the deployment line is part of the product semantics), non-Enterprise wanting custom models.

头号误解Top misconception

部署链绑 Vercel：publish 走 Vercel 项目与域名（官方 deployments 页）——GitHub 同步只搬代码，经 GitHub/Vercel CLI 的部署权限看 Vercel 角色，两套权限别混（官方页专门警告）The deployment chain is bound to Vercel: publishing goes through the Vercel project and domains (official deployments page) — GitHub sync only moves code; deployment via GitHub/Vercel CLI follows your Vercel role, two permission systems not to be conflated (the official page warns explicitly)
自定义模型（AI Gateway 目录）是 Enterprise 团队功能且需 owner 批准——普通计划的模型选择面比官方文档读感窄Custom models (the AI Gateway catalog) are an Enterprise-team feature requiring owner approval — the model menu on regular plans is narrower than the docs read like
沙箱有 VM-backed 与旧浏览器内两代（官方 sandbox 页明示取代关系）——旧教程里「浏览器内跑」的行为描述可能已过时The sandbox has two generations: VM-backed and the older in-browser one (the official sandbox page states the replacement) — 'runs in the browser' behavior described in older tutorials may be outdated

未知项清单Known unknowns

跨会话记忆机制（未核验到官方声明）
构建任务关闭页面后是否续跑（未核验到官方声明）
免费/付费计划的额度差完整表（pricing 页在，未逐条清点）
聊天生成侧的可选模型完整清单（选择器随计划与网关目录变化，未逐条清点）

Cross-session memory mechanism (not verified to an official statement)
Whether build tasks keep running after the page is closed (not verified to an official statement)
The complete allowance-difference table across free/paid plans (the pricing page exists; not enumerated one by one)
The complete selectable model list on the chat-generation side (the picker changes with plans and the gateway catalog; not enumerated one by one)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-22，内容更新日content updated on 2026-10-22。

类型Type	名称Name	链接Link
official	v0 文档 · Quickstart（产品入口 v0.app/主工作流）v0 docs · Quickstart (product entry v0.app / main workflow)	https://v0.dev/docs/quickstart
official	v0 文档 · Sandbox（Vercel Sandbox VM/取代浏览器内环境）v0 docs · Sandbox (Vercel Sandbox VM / replaces the in-browser environment)	https://v0.dev/docs/sandbox
official	v0 文档 · Agentic features（搜索/浏览器/终端/修错/权限档）v0 docs · Agentic features (search / browser / terminal / error fixing / permission modes)	https://v0.dev/docs/agentic-features
official	v0 文档 · Choosing models（选择器/AI Gateway/Enterprise 门槛）v0 docs · Choosing models (picker / AI Gateway / Enterprise gating)	https://v0.dev/docs/model-picker
official	v0 文档 · GitHub（同步与部署权限分离警告）v0 docs · GitHub (sync and the deployment-permission separation warning)	https://v0.dev/docs/github
official	v0 文档 · Security（威胁模型/沙箱执行口径）v0 docs · Security (threat model / sandboxed-execution framing)	https://v0.dev/docs/security
official	v0 文档 · Pre-installed Agents（沙箱内跑 claude 等）v0 docs · Pre-installed Agents (running claude etc. inside the sandbox)	https://v0.dev/docs/pre-installed-agents
changelog	Vercel Changelog · v0 相关条目（产品变更公告通道）Vercel Changelog · v0-related entries (product-change announcement channel)	https://vercel.com/changelog?q=v0

实测记录Measured runs

本档未跑端到端编码任务；能力结论来自官方文档，编码向测量协议见 protocols/coding/_protocol.md。

实测建议（三条，都指向官方可读页没给的东西）：

Ask/Auto/Full 三档在终端命令上的实际拦截粒度（官方给档位定义，未给逐类命令矩阵）
预装 claude 与 v0 内置助手同项目并行的上下文互见程度
旧浏览器内沙箱存量项目的迁移行为（官方页只说取代，未给存量指引）

This site has not completed measured runs. The test protocol is at protocols/coding/_protocol.md.

Suggested measurement (three, each pointing at something the official readable pages do not give):

The actual interception granularity of Ask/Auto/Full on terminal commands (the official gives mode definitions, not a per-command-class matrix)
How much context the pre-installed claude and v0's built-in assistant can see of each other when running in parallel on one project
Migration behavior for existing projects on the old in-browser sandbox (the official page only says it was replaced; no guidance for existing projects)