Vasel Institute
01 / 09 · Overview
zero
programming language
For brokers
An experimental techniques language that gives structured diagnostics to AI brokers,
Accommodates typed restore metadata and machine-readable documentation with lower than 10 KiB of native binaries.
system language
agent native
v0.1.1
apache-2.0
experimental
context
02 / 09 · Why does zero exist?
Agent restore loop challenge
Most programming languages produce compiler output written for human readers. That is unstructured textual content that the AI agent should parse to find out what went improper and the best way to repair it. This creates a fragile loop.
- agent writes code — the compiler outputs the error as unstructured textual content
- Agent parses textual content — Error format could differ between compiler variations
- No restore ideas — No idea of “restore motion” in-built
- human historical past — Loop requires handbook intervention to resolve error
Zero was designed from the bottom as much as enable brokers to learn code, interpret diagnostics, and restore packages with out human translation.
core performance
03 / 09 · JSON diagnostics
Structured compiler output
working zero test ——json Outputs machine-readable diagnostics as a substitute of plain textual content. All errors embrace secure code, human message, line quantity, and restore ID entered.
$ zero test --json
{
"okay": false,
"diagnostics": [{
"code": "NAM003",
"message": "unknown identifier",
"line": 3,
"repair": { "id": "declare-missing-symbol" }
}]
}
- code — Secure identifier brokers can reliably match (
NAM003) - message — Human-readable error description
- restore — Entered remediation ID agent can work with out textual content parsing
core performance
04 / 09 · Restore command
Zero explanations, zero corrections
Two CLI subcommands full the agent restore loop with out the agent having to parse the prose doc.
zero clarify NAM003
Returns a structured description of a diagnostic code. agent investigates NAM003 Straight — no doc scraping.
zero repair --plan --json add.0
Output a machine-readable repair plan that explains precisely what modifications to make. No reasoning required.
collectively, zero clarify and zero repair --plan --json Allow brokers to grasp errors and act on them with out human translation of compiler output.
core performance
05/09 · Agent steerage
Zero talent: version-specific agent steerage
Most instruments require the agent to gather exterior documentation that could be out of sync with the put in compiler. Zero solves this like this zero abilities — Steering offered instantly from the CLI relying on the put in model.
zero abilities get zero --full
Returns a workflow centered on:
- zero syntax — Fundamentals of the present model of the language
- analysis — Easy methods to interpret and course of compiler output
- construct and package deal — Manifest construction, targets, and outputs
- Check and agent edit loop — Validation and remediation workflow sample
language design
06 / 09 · Characteristic-based I/O
Specific results and feature-based I/O
In Zero, when a operate touches the surface world, its signature signifies that. There aren’t any hidden international course of objects, implicit asyncs, and magic globals.
pub enjoyable foremost(world: World) -> Void raises {
test world.out.write("hiya from zeron")
}
- World: World — Purposeful object; permits entry to I/O, file system, community
- test — Deal with incorrect operations. Floor failures as much as the decision stack
- improve — marks the operate as probably propagating errors — seems within the signature
- compile-time enforcement — Unavailable options are rejected at compile time, not at run time.
language design
07 / 09 · Reminiscence and measurement
Predictable reminiscence and small binaries
Zero targets environments the place binary measurement and reminiscence predictability are necessary. There aren’t any hidden runtime taxes.
< 10 KiB
Native executable with static dispatch, no required GC, no required occasion loop
zero construct --emit exe
--target linux-musl-x64
add.0 --out .zero/out/add
zero measurement --json— Report the scale of artifacts earlier than code era if doable- no hidden allocators — Assignments are specific and visual within the code
- C ABI export — C boundary target-aware interop metadata
fast begin
08 / 09 · Introduction
Set up and run Zero
Set up the compiler with a single curl command.
curl -fsSL https://zerolang.ai/set up.sh | bash
export PATH="$HOME/.zero/bin:$PATH"
zero --version
Confirm, run, and construct your first program.
zero test examples/hiya.0
zero run examples/add.0
zero construct --emit exe --target linux-musl-x64
examples/add.0 --out .zero/out/add
Create a brand new package deal.
zero new cli hiya
cd hiya
zero test . && zero check . && zero run .
state of affairs
09 / 09 · Present state of affairs
What can and can’t be used
- v0.1.1 (experimental) — Compiler, stdlib, and language specs will not be but secure
- package deal registry lacking — Ecosystem unfold is in its early phases
- cross compilation — restricted to a subset of documented targets
- VS Code extensions — syntax highlighting
.0The file will probably be included within the repository - contributor — Chris Tate & Matt Van Horn (Vercel Labs)
zero languay
github.com/vercel-labs/zero
Zero is a sensible experiment value following for AI engineers concerned about agent-native toolchain design, and isn’t but production-agnostic.

