Vercel Zero Explorer#

Overview#

Vercel Zero is an experimental systems programming language launched by Vercel Labs on May 16, 2026. Scope: conceptual guidance, command reference and integration patterns for Zero; it does not install the toolchain, run zero commands, or write files. Unlike traditional programming languages that prioritize human readability, Zero embraces AI-native paradigms with structured JSON diagnostics, explicit effects, and predictable memory management.

This Skill provides comprehensive guidance on understanding, using, and building with Zero language.

Current Status (as of 2026-10-09)#

ItemStatusLatest releasev0.3.4 (the 0.1.x line is obsolete)LicenseApache-2.0GitHub~5,200 stars, developed by Vercel LabsTargetsNative binaries for Linux, macOS, WindowsAuthoring modelGraph-first: zero.graph is the compiler input; .0 files are human-readable projectionsMaturityExperimental — breaking changes expected, not for production or sensitive data

Recent developments:

• v0.3.0 made graph-first authoring the default workflow. The binary zero.graph store is now what the compiler reads; .0 text files became projections for human review. Agents edit through zero query / zero patch instead of rewriting source text, and patches carry an expected graph hash so stale or invalid edits are rejected before the store is written.
• Version churn is real. v0.1.4 introduced row syntax, v0.2.0 promoted canonical .0 text to the native source surface, and v0.3.0 rejects source-projection input at the compiler boundary. Existing text-first packages must run zero import to pull source into the graph; v0.3.2 reportedly made zero import roughly 12x faster on large programs.
• The toolchain contract is the distinctive part. Every subcommand of the single zero binary shares one --json flag and one diagnostic schema, so errors arrive with stable codes (e.g. NAM003) and typed repair metadata (e.g. declare-missing-symbol); zero fix --plan --json returns a repair plan an agent can accept, edit, or reject rather than a blind patch.
• These items are compiled from public coverage; exact version numbers, flags and behaviour change frequently — treat the official repository and docs as authoritative.

Safety note: Vercel Labs explicitly warns to expect breaking changes, rough edges and security issues, and to avoid production systems and sensitive data. Evaluate Zero in an isolated, disposable workspace.

More recent developments (compiled 2026-10-09, treat official docs as authoritative):

• Graph-first is now the practical entry point, not an option. Guidance and examples that still start from editing .0 text are stale; the recommended loop is zero query → zero patch --json (with expect_hash) → zero fix --plan --json → zero export for review.
• Hash-guarded patches are the main safety lever. Because a patch carries an expected graph hash, an agent editing from a stale view is rejected before the store is written — this is the mechanism worth validating first in any evaluation.
• Version churn continues. Exact subcommand names, flags and diagnostic codes change between minor versions; pin the version you evaluate against and record it alongside your results.
• These items are compiled from public coverage; verify against the official repository and docs before relying on any specific flag or code.

Triggers#

Chinese（须落在 Vercel Zero 这一具体语言上才触发）:

• "Vercel Zero 是什么"
• "Zero 的 graph-first 工作流怎么走"
• "Zero 的 .0 文件现在还是不是源文件"
• "Zero 的 zero patch --json 怎么用"
• "Zero 的诊断码 NAM003 是什么意思"

English（must name Vercel Zero explicitly）:

• "What is Vercel Zero"
• "Vercel Zero graph-first workflow"
• "Zero query / patch / fix --plan usage"
• "Zero .0 projection vs zero.graph"
• "Zero structured JSON diagnostics schema"

Non-triggers / 不触发：

• Generic "AI agent programming language" discussions, language-design theory, or comparisons that never mention Zero
• Python / JavaScript / Go / Rust programming questions
• Generic compiler, parser or LLVM questions unrelated to Zero
• Requests to actually install the toolchain or run builds for the user

路由判定三步：① 用户是否明确点名 Vercel Zero（不是泛指「AI 语言」）？② 诉求是否为理解概念、查命令、看诊断或设计 agent 集成？③ 前两步均为是才启用本 Skill；否则转通用编程语言或编译器相关技能，或请用户补充具体语境。

Features#

0. Data Minimization & Execution Boundary / 数据最小化与执行边界#

数据最小化前置声明（使用本技能前请先执行）

1. 粘贴诊断 JSON、代码片段或命令输出前，先删除其中的绝对路径、内网主机名、令牌、项目名与个人信息；用占位符替代。
2. 不要在提问中粘贴生产代码或包含密钥的配置；Zero 本身仍在实验阶段， 官方明确建议不要用于生产系统与敏感数据。
3. 评估 Zero 时请使用隔离、可丢弃的工作区，不要指向生产环境或真实数据集。
4. 本技能不安装 Zero 工具链、不执行 zero 任何子命令、不读写文件；所有命令均为供你复制后在自己环境中运行的参考文本。
5. 生成的代码或补丁如需落盘，须先预览确认无敏感信息，再自行保存与执行。

代码块性质与执行边界

内容性质谁来执行zero / bash 代码块可直接复制的命令参考文本使用者在自己的隔离工作区中运行，本技能不执行zero 语法与 JSON 诊断示例结构与字段说明使用者对照官方文档与本地版本校验版本号、star 数、二进制体积等数字公开报道的观察值，随版本变化使用者以官方仓库复核World 能力、effect 声明等概念语言设计说明使用者在自己的程序里实践

硬边界：不安装工具链、不执行命令、不读写文件、不发起网络请求、不访问用户环境。

1. Core Concepts of Zero Language#

ConceptDescriptionMechanismWhy it matters for an agent验证方式（自己跑一遍）Native ToolsZero provides built-in system tools optimized for AI agentsBuilt into the language rather than pulled from external package registriesNo dependency resolution step, so an agent's first build rarely fails on missing packages对比同等功能在 Python 下需要引入几个外部包Explicit EffectsSide effects are explicitly declared, making AI behavior predictableA function that touches the outside world must accept a World capability; the compiler enforces itA signature alone tells the agent whether code can reach network, filesystem or stdout写一个无 World 参数的函数，看编译器是否拒绝文件访问Predictable MemoryMemory management follows deterministic patternsDeterministic allocation instead of tracing garbage collectionExecution cost is easier to predict before running, useful when an agent is choosing between candidate programs对同一程序多次运行，观察分配与耗时是否稳定Structured JSON DiagnosticsCompiler outputs structured JSON for easy AI parsingOne shared --json flag and one diagnostic schema across every subcommandThe agent branches on stable codes instead of parsing changing prose故意写错标识符，看返回的 code 与 repair 字段**.0 File Extension**Uses .0 extension (e.g., main.0)Under v0.3.x the .0 text is a projection exported from the graph, not the compiler inputHumans can still review and deliberately edit readable text, then import it back导出 .0 后手工改一行，再跑 verify-projection 看是否报错

2. Zero Syntax Basics#

zero

// Example Zero code structure
import { http, file } from "std";

// Define a tool with explicit effects
tool fetch_data(url: string) -> json {
  effect network_call(url)
  return http.get(url)
}

// AI-friendly structured output
diagnose parse_result as json

Example — the World capability makes effects visible in the signature:

zero

import { file, std } from "std";

// No World parameter => the compiler guarantees this cannot touch disk or network
tool pure_total(prices: list<f64>) -> f64 {
  return prices.fold(0.0, |acc, p| acc + p)
}

// World is required => the signature itself advertises a filesystem effect
tool save_report(w: World, path: string, body: string) -> result<unit, io_error> {
  effect file_write(path)
  return file.write(w, path, body)
}

The practical payoff: an agent reviewing a candidate function does not need to read its body to know whether it can reach the outside world — save_report obviously can, pure_total provably cannot.

Example — why the hash guard matters in practice: two agents edit the same program from slightly different views of the graph. Agent A patches node 653eeb6e with expect_hash ab91... and succeeds. Agent B, holding a stale view, patches the same node with an old hash and is rejected before the store is written — no silent overwrite, no corrupted graph. This is the single most valuable property to verify when evaluating Zero for agent workflows.

Example — a diagnostic an agent can act on (v0.3.x schema):

json

{
  "code": "NAM003",
  "severity": "error",
  "message": "unknown identifier `prices_total`",
  "repair": { "kind": "declare-missing-symbol", "symbol": "prices_total" },
  "span": { "node": "653eeb6e", "field": "value" }
}

Note the span points at a stable node id and field, not a line/column pair. That is the whole point of graph-first authoring: the reference does not drift when someone inserts a comment above it.

3. AI Agent Integration Patterns#

• Tool Definition: Define reusable tools with explicit interfaces
• Effect Declaration: Declare side effects before execution
• Structured Diagnostics: Parse compiler output as JSON for AI decision-making
• Error Recovery: Use structured errors for autonomous debugging

Integration example — autonomous fix loop with Claude Code:

bash

# 1. read the graph instead of guessing at source text
zero query --json '{"kind":"function","name":"fetch_api_data"}'

# 2. propose a semantic patch guarded by a hash
zero patch --json '{"op":"set","node":"653eeb6e","field":"value","expect_hash":"ab91...","to":"..."}'

# 3. ask the compiler for a plan instead of applying a blind fix
zero fix --plan --json

# 4. keep human review in the loop
zero export --out review/ && zero verify-projection

Integration example — CI drift gate: run zero verify-projection in CI so a hand-edited .0 file that no longer matches the graph fails the build rather than silently diverging.

Integration example — capability scoping: grant World only to a single top-level main entry point, and have every other function take plain values. When an agent proposes a change that suddenly needs World deep in the call graph, the signature change itself is the signal to slow down and review — no need to read the whole diff.

Integration example — diagnostic code lookup: keep a small table of the codes you actually hit and map each to one recovery action ( NAM003 → declare the missing symbol; hash mismatch → re-run zero query; effect errors → check the World parameter). Recovery then becomes a lookup instead of a fresh reasoning step on every failure.

Command Cheat Sheet#

CommandPurposeTypical agent use失败/注意信号zero initInitialise a package / graph storeStart of a task工作区未初始化；先确认目录可丢弃zero query --jsonRead declarations, types, calls, effects, node idsReplace "read the file"返回为空说明名字或 kind 写错，而非功能不存在zero patch --jsonApply a semantic edit guarded by a graph hashReplace "rewrite lines 40-52"expect_hash 不匹配即为视图过期，需重新 queryzero importPull existing .0 source into the graphMigrating text-first packages大程序导入慢时可查版本是否 ≥ 声称提速的版本zero exportEmit a human-readable .0 projectionHuman review, pull requests不匹配说明 .0 被手改过，不要直接导入回去zero verify-projectionCheck the projection still matches the graphCI drift gatecheck 过但 test 挂，多为 effect 声明不足zero check / zero test / zero runType-check, test, executeStandard loop返回 plan 而非自动修复，需自行决定是否采纳zero fix --plan --jsonMachine-readable repair planAgent decides accept / edit / reject目标平台需显式指定，默认不等于当前机器zero buildEmit executable, object, or LLVM IRPackaging

Every one of these accepts --json, so a single parser handles all of them.

Workflow#

Step 1: Understand Zero's Design Philosophy#

• Zero prioritizes AI parsing over human readability

• Structured output enables reliable AI agent workflows

• Native tools are designed for autonomous execution

• Example: where a Python agent must first resolve requests from an index and hope the version is compatible, a Zero agent calls a built-in http tool that ships with the language — one less failure mode per iteration.

• Example: an agent asked to "add retry logic" can read the call graph with zero query and see exactly which node issues the network effect, instead of grepping prose for http and hoping it found every call site.

Step 2: Explore Zero Syntax#

• Learn the .0 file extension convention

• Understand explicit effect declarations

• Master structured JSON diagnostics format

• Example: map the codes you actually hit into a lookup table ( NAM003 → declare missing symbol, timeout codes → retry with backoff) so recovery is a table lookup instead of a fresh reasoning step each time.

• Example: when a .0 projection is edited by hand, run zero verify-projection before importing it back — the graph is the source of truth, and drift discovered at import time is far cheaper than a corrupted store.

Step 3: Build AI-Native Tools#

• Create custom tools with predictable behavior

• Define clear input/output interfaces

• Use explicit error handling patterns

• Example: return result<json, io_error> rather than throwing, so the caller — which is usually the agent — is forced to handle the failure branch at compile time.

• Example: keep the effect list in a tool declaration minimal ( network_call only, not network_call plus file_write); a narrower effect set makes the tool safe to call from more places without re-reviewing it.

Step 4: Integrate with AI Agents#

• Connect Zero programs to Claude Code, Codex, or other AI coding agents

• Use structured diagnostics for autonomous debugging

• Implement guardrails for safe AI execution

• Example: grant the World capability only to a thin top-level entry point and pass pure functions everything else; then the blast radius of an agent-generated change is legible from the call graph.

• Example: treat zero fix --plan --json output as a proposal to review, not an instruction to apply — the plan is machine-readable precisely so a human or a policy layer can accept, edit or reject it.

Input/Output Examples#

Example 1: Understanding Zero Concepts#

Input:

text

Explain the key differences between traditional programming languages and Zero language.

Output:

text

Key Differences Between Traditional Languages and Zero:

| Aspect | Traditional Languages | Zero Language |
|--------|---------------------|---------------|
| Target Users | Humans | AI Agents |
| Output Format | Human-readable errors | Structured JSON diagnostics |
| Effects | Implicit side effects | Explicit effect declarations |
| Memory | Garbage collection | Predictable memory patterns |
| Tool Interface | External libraries | Native built-in tools |
| Extension | .py, .js, .go | .0 |

Zero is not meant for humans to write directly - it's designed to be generated and understood by AI agents.

Example 2: Creating a Zero Tool#

Input:

text

Create a Zero tool that fetches data from an API and returns structured JSON.

Output:

zero

// data_fetch_tool.0

import { http, json } from "std";

// Tool definition with explicit effects
tool fetch_api_data(
  endpoint: string,
  method: string = "GET"
) -> json {
  // Explicit network effect declaration
  effect network_call(endpoint, method)

  // Execute HTTP request
  response = http.request(endpoint, {
    method: method
  })

  // Return structured JSON
  return json.parse(response.body)
}

// Structured diagnostics for debugging
diagnose fetch_api_data as {
  success: boolean,
  data: json | null,
  error: string | null
}

Example 3: AI Agent Workflow Integration#

Input:

text

How can I integrate Zero programs with Claude Code for autonomous debugging?

Output:

text

Integration Guide for Claude Code + Zero:

1. Generate Zero code using Claude Code
2. Execute and capture JSON diagnostics
3. Parse structured errors for autonomous recovery
4. Implement fix strategies based on diagnostic codes

Example Workflow:
```json
{
  "step": "execute",
  "tool": "fetch_api_data",
  "diagnostic": {
    "code": "NETWORK_TIMEOUT",
    "suggestion": "retry_with_backoff",
    "affected_lines": [5, 6]
  }
}

Claude Code can automatically:

• Parse diagnostic codes
• Select recovery strategy
• Re-execute with modifications
• Verify fix success

text

### Example 4: Recovering From a Stale Patch (hash mismatch)

**Input:**

My zero patch --json failed. What does the error mean and what should I do next?

text

**Output:**

A failed patch guarded by expect_hash almost always means your view of the graph is stale, not that the edit is wrong. Recovery order:

1. Re-read the current state: zero query --json '{"kind":"function","name":""}'
2. Compare the node id and hash you held against what the query returned.
3. Re-apply the patch with the fresh expect_hash from the query.
4. Only if the node itself changed, re-derive the edit — do not force it.

The guard is working as designed: it rejected the write before the store was modified, so there is nothing to clean up. Never retry the same stale hash in a loop.

text

## Use Cases

| Use Case | Description | Best suited for | Honest caveat | 先做的最小验证 |
|----------|-------------|-----------------|---------------|---|
| **AI Code Generation** | Generate Zero code that AI agents can reliably execute | Agent builders measuring whether hash-guarded patches reduce silent breakage | Training-data advantage still sits with Python/JS/Go | 一个小工具分别用 Zero 与 Python 走完同一改动，比较失败次数 |
| **Autonomous Debugging** | Use structured diagnostics for self-healing code | Loops that need to branch on error codes rather than prose | Garbage in still produces garbage out; tests still decide correctness | 构造 3 类已知错误，看 agent 能否按 code 分别恢复 |
| **Tool Development** | Build native tools optimized for AI workflows | Small disposable CLI utilities where a ~16 KiB binary is a feature | Ecosystem is young; expect to write your own bindings | 写一个 100 行以内的小 CLI，走完 query→patch→fix→export |
| **Language Research** | Explore AI-native programming paradigms | Researchers comparing capability-based effects and graph IRs | Benchmarks are design targets, not published results — measure yourself | 固定版本跑一组可复现基准，记录版本号与机器信息 |

## References

- [Vercel Zero GitHub Repository](https://github.com/vercel-labs/zero)
- [Zero Official Documentation](https://vercel.com/docs/zero)
- [AI Agent Programming Language Analysis](https://blog.csdn.net/irpywp/article/details/161167783)
- [InfoQ: Vercel Labs Ships Zero, a Graph-First Language Built So Agents Write the Code](https://www.infoq.com/news/2026/08/vercel-ships-zero-ai)
- [Zero getting-started guide](https://github.com/vercel-labs/zero) — authoritative for current commands and flags

## Notes

- Zero is experimental (**v0.3.4** as of 2026-10-09; the 0.1.x line is obsolete)
- Not intended for production human-written code
- Focus is on AI agent reliability and predictability
- File extension `.0` is unique to Zero language
- Under v0.3.x the compiler reads `zero.graph`, not `.0`; treat `.0` as a projection
- Reported figures (16.2 KiB hello world, ~1 ms build, token efficiency, tiny artifacts) are **design targets** — benchmark your own program before relying on them
- Positioning: closer to Zig than Rust on binary size and explicit allocation; lacks Rust's borrow-checker maturity and ecosystem, and trades Go's green threads and larger runtime for dependency-free artifacts
- **Evaluate in an isolated workspace**; do not point Zero at production systems or sensitive data
- Pin the exact version you evaluate against and record it with your results — flags and codes move between minor versions
- Prefer `zero query` + hash-guarded `zero patch` over any text rewriting of `.0` files
- Treat `zero fix --plan --json` output as a proposal, not an instruction to apply automatically
## Changelog / 变更记录

| 版本 | 日期 | 变更摘要 |
|------|------|---------|
| 1.0.2 | 2026-10-09 | 收窄中英文触发词（须明确点名 Vercel Zero）、补充非触发清单与路由判定三步（SQP-1 x2）；新增数据最小化前置声明与代码块性质/执行边界表及硬边界；状态与动态更新至 2026-10-09 并新增 graph-first 入口、hash 守卫、版本churn 三条；新增列：验证方式、失败/注意信号、先做的最小验证；概念表后补 hash 守卫示例、集成模式补 2 例、Workflow 四步各补第二例；新增示例4（stale patch 恢复）；Notes 补 3 条 |
| 1.0.1 | 2026-09-14 | 新增 graph-first 工作流与命令速查 |

---

---

**Author:** Ge Cheng | **Skill Address:** clawhub.ai/skills/vercel-zero-explorer | **Skill Version:** 1.0.2 | **Last reviewed:** 2026-10-09