Zero (Programming Language)

Experimental systems language from Vercel Labs ("The Programming Language for Agents") whose compiler is built to talk to AI agents, not humans: JSON diagnostics with stable error codes, typed repair metadata, capability-based I/O, and sub-10 KiB native binaries. vercel-labs/zerolang, Apache-2.0, ~5K stars. Source: GitHub vercel-labs/zerolang, https://github.com/vercel-labs/zerolang, 2026-06-13

What it is

Zero sits in the same design space as C or Rust — it compiles to native executables, gives explicit memory control, and targets low-level environments — but inverts the audience. Most languages assume a human reads error text and traces stacks; Zero is designed "from day zero" so an agent can read code, parse diagnostics, and apply repairs without human translation. Created by Chris Tate and Matt Van Horn at Vercel Labs; released 2026-05-15 (the morning before Google I/O), it reached ~900 GitHub stars in 24h and ~5,017 now. The compiler is written in C++. Source: MarkTechPost, https://www.marktechpost.com/2026/05/17/vercel-labs-introduces-zero-a-systems-programming-language-designed-so-ai-agents-can-read-repair-and-ship-native-programs/, 2026-05-17

Current Source Snapshot

As of the deep review, vercel-labs/zerolang is an Apache-2.0 repo with latest GitHub release v0.3.4 published 2026-06-13, main at afcc72da649fe4d4c670ac1489c2197d37436051, 5,147 stars, and 339 forks. There is no current zerolang, @vercel-labs/zerolang, or @vercel/zerolang npm package; npm zero@1.1.23 is a different package from remoteinterview/zero and should not be used as version authority. Source: GitHub vercel-labs/zerolang, 2026-06-30; npm registry, 2026-06-30

Agent-native design

• Structured diagnostics — zero ... --json emits a stable error code (e.g. NAM003), a human message, a location, and a typed repair object. The code is the contract: agents key off it instead of parsing prose. Source: TechTimes, https://www.techtimes.com/articles/316793/20260518/vercel-labs-zero-compiler-speaks-json-ai-agents-closing-human-translation-gap-agentic-coding.htm, 2026-05-18
• Repair loop — zero explain and zero fix --plan --json give agents machine-readable explanations and fix plans. The v0.3.4 release moves the center of gravity toward graph patching: agents submit checked edits, use stdin patch bodies, replace expressions by handle, apply structural rewrites, and rely on inline handle diagnostics instead of broad whole-file regeneration. Source: MarkTechPost, 2026-05-17; GitHub release v0.3.4, 2026-06-13
• Capability-based I/O — no ambient globals (no print, console.log, or os.Stdout). The runtime hands main a World capability; any function doing I/O must be passed World (or a slice), so effects are visible in signatures and pure functions literally cannot do I/O — the type system enforces it. An agent can reason about a function's effects locally without reading the whole codebase. Source: Coddy Zero docs, https://coddy.tech/docs/zero/world-capability, 2026-06-13
• Status — v0.3.x, experimental and pre-production; no npm package registry entry under the expected names; ships a VS Code extension for .0 files; docs at zerolang.ai. Explicitly treat it as a design/reference tool, not a production dependency. Source: MarkTechPost, 2026-05-17; GitHub vercel-labs/zerolang, 2026-06-30

Stack fit (Kevin)

• Directly on-thesis. Stable error codes + typed repair metadata + fix --plan --json is the language-level version of the Agent-Native CLIs philosophy Kevin enforces (typed exit codes, machine-parseable errors, one-retry self-correction). Notably, Zero is co-authored by Matt Van Horn — the same author behind PrintingPress/last30days that Kevin already trusts.
• Capability-based World I/O is a clean, fail-closed model for sandboxing what agent-generated code can touch — relevant to agent-guardrails and the "name every effect" discipline in Kevin's review lessons.
• Author already in the stack: Chris Tate also made Browser Testing Skills (Kevin's browser tool) and Zero Native (Zig desktop apps — distinct from this language despite the shared "zero" name).
• Posture: watch/experiment, do not adopt as a production language yet. The transferable win is the design principle: an agent-friendly compiler should expose stable handles, typed effects, structured diagnostics, and patch-level edit APIs.

---

Timeline

• 2026-05-15 | Announced by Chris Tate on X. Source: X/@ctatedev, 2026-05-15
• 2026-06-13 | Quality remediation: verified repo (vercel-labs/zerolang, Apache-2.0, C++, ~5K★, co-author Matt Van Horn), the World capability model, JSON diagnostics + zero fix --plan --json, and sub-10 KiB binary claims; added Kevin stack-fit. Source: https://github.com/vercel-labs/zerolang
• 2026-06-30 | Deep-reviewed the launch screenshot and current repo state; promoted the page to tier 2 because graph patching, typed repair metadata, and explicit capabilities are reusable agent-system design patterns even if the language itself remains experimental. Source: X bookmark artifact audit, 2026-06-30