hav
Human Agent Versioning is a version control system built from scratch for the agentic coding era. It has its own core model and no git compatibility, designed for how code gets written now: by people and agents in parallel, on work that sometimes needs to stay private until it ships.
Why it exists
- No staging, no commit dance. The working copy is the unit of work (a
knot), and every command captures it automatically.
describeandtiereplace the add/commit sequence. - Merges never block. Conflicts are stored as data inside snapshots. They
materialize as markers in your tree, on your schedule, and there is no
--continueanywhere. - Files never move under you. Syncing is explicit. hav tells you when your buoy advanced and then waits, so it never rebases a tree that a build or an agent might be running against.
- Everything is undoable. Every mutation is one journaled op, and
hav undorestores both the state and the files on disk. - Private work inside shared repos. Sealed crews encrypt whole lines of
work client-side, and going public is always a member's explicit
tie --reveal. The key is the gate: ciphertext travels to everyone, only members can open it, and no server decides.
The reasoning behind all of this lives in Why hav exists and Design principles.
Start here
Install
One cargo install, no dependencies beyond a Rust toolchain.
hav in 5 minutes
Init to shared hub on a toy project. Every command runs, in order.
hav for git users
The translation table, and the habits to unlearn.
The model
Snaps, knots, buoys, workspaces: the whole thing on one page.
Status
v0.1.0, first beta. The core model, sealed crews, per-crew variant sets, the harbor, and two-regime storage are implemented, tested, and exercised end-to-end. Read Status and limits before trusting it with anything. It covers what hav is for today, the limits (the crypto is unaudited), the measured performance envelope, and how to report bugs.
License
GPLv2, like git.