Roadmap
What is planned for Zit, why, and what each item depends on. Plans, not promises; no dates.
Each item below is a known gap: it is listed on Limits or came out of a hostile review of the project. Status is as of 0.1.3. Nothing here is built until it says so, and the order is the current priority, not a schedule.
Delivered in 0.1.2
Each was on this page or on Limits as a gap.
| Item | What landed | Where |
|---|---|---|
| Batches | zit accept A B C and zit accept --batch: compose in order, check once, land together; a failing check rejects the batch without bisecting |
CLI |
| Parse-check the composed state | merged text with syntax errors neither side had is refused ([accept] parse_check) |
zit.toml |
| Renames | a renamed file is compared unit by unit; a pure move writes nothing | Limits |
| More languages | Java, Ruby, C#; TOML and JSON manifests by top-level key; TypeScript overloads and abstract signatures | Specification |
| Stable-path workspaces | [workspace] stable_paths or zit.stablePaths: reusable ws/slot-N |
zit.toml |
| A port per workspace | ZIT_PORT, free at materialisation, not reserved |
Agents |
| An agent’s output with the change | zit run --log, zit show --log, refs/zit/logs/<id>; the agent’s output, not the commands it ran |
Agents |
zit doctor |
git, home, copy-on-write, free space, graph, zit.toml programs, agents, grammars |
CLI |
| An integrator for CI | integrations/github: a composite action; tested as a script, not yet on Actions |
Working with git |
| Status memo | repeated zit status reuses each change’s status until current or the evidence changes |
How it works |
| Usage from Pi | tokens and Pi’s price from pi --mode json |
Agents |
Distribution
| Item | Why | Status |
|---|---|---|
Publish the crate, so cargo install zit works |
Install without access to the repository | Done: zit 0.1.3 is on crates.io; cargo install zit --locked installs it |
Publish the Pi extension (pi install npm:pi-zit) |
Install without a local checkout | Done: pi-zit 0.1.0 is on npm. Still to do: a turn with a live model |
Release Autohand Code with autohand --zit |
A whole Autohand Code session in a Zit workspace | Built and run end to end; ships in the next Autohand Code release |
| Windows | Claude Code and Cursor run there; Zit is Unix-only (signals, libc) |
Not started |
Correctness
| Item | Why | Status |
|---|---|---|
| Resolve references by path and import, not only by name | A mention of Config depends on every Config in the repository (Limits) |
Not started |
| More languages with symbol granularity (C, C++, Kotlin, PHP, Swift, Scala) | Files in those languages are one resource with no inferred reads; Java, Ruby and C# are done | Not started |
| Re-measure false refusals | The 21–23% figure predates the interface-only staleness rule (ADR 16) | Not started |
| Signed evidence | Fetched check results are untrusted by default; trusting them (zit.trustFetchedEvidence) trusts whoever can push refs |
Not started |
Run [[derive]] and [prepare] only from trusted states |
A change’s own zit.toml commands run when you accept or materialise it |
Not started |
| Keep agents’ branches, tags and stashes out of the real repository | A workspace shares the repository’s refs | Not started |
| Stop children of interactive agents | Headless runs stop the agent’s process group; interactive runs stop only the agent | Not started |
Scale and teams
| Item | Why | Status |
|---|---|---|
| Claims across machines | Claims and live write sets are local to one machine | Not started |
| Run the GitHub integrator on GitHub Actions | integrations/github is tested as a script against a bare origin; the action, install.sh on Linux and trust-evidence: true are not |
Not started |
| Usage from Autohand Code | Autohand 0.9.9-alpha reports nothing parseable; Claude Code, Codex and Pi do | Not started |
Evidence
| Item | Why | Status |
|---|---|---|
| Repeat the experiments on other repositories, languages and machines | Every real-agent result so far is from one or two runs on one Mac (Lessons) | Not started |
| Human review of what landed | Quality has been scored only by a blind model judge (Lesson 04) | Not started |
| A pnpm baseline for the dependency benchmark | The 327 MB against 1,619 MB comparison is against npm ci per worktree |
Not started |
| Linux disk benchmark with real dependencies | The Linux runs use a synthetic repository of small files | Not started |
From the research
Candidates from Prior art and objections, each answering a weakness found there. Sizes are estimates.
| Item | Why | Size |
|---|---|---|
| Report false refusals and false accepts against test oracles | Merge-tool evaluations that ignore incorrect clean merges overstate quality (Schesch et al., 2024) | Medium |
| Replay public agent-conflict data: AgenticFlict, CooperBench, STALE | Measured accuracy on other people’s data instead of our own runs | Medium |
| A conflict graph from footprints, to pick a batch automatically | Uber’s SubmitQueue commits independent changes in parallel; Zit’s batch takes the changes you name (or every verified one) and cannot say which member broke a failing check | Large |
| A structure-aware merge for adjacent insertions | Zit’s most common remaining rejection; semistructured merge removes it (Apel et al. 2011; Cavalcanti et al. 2017) | Large |
| Compose open workspaces against each other in the background | Crystal’s speculative merging warns before anyone records | Medium |
| Measure how much parallelism refused claims give up | Pre-write admission serialised 93.3% of clean cases in Claim Plane (2026) | Small |
| A namespace per workspace | Each workspace has a port (ZIT_PORT); other machine-wide state is still shared |
Medium |
| A log of the commands an agent ran | zit run --log keeps the agent’s output; what it ran is still not recorded |
Small |
Select checks from footprints instead of declared inputs |
Check inputs are trusted, not verified | Medium |
To propose or take on an item, open an issue (CONTRIBUTING.md).