The graph, at true scale
Every commit sits where it actually happened. Parallel lines of work keep their lanes, and merges converge exactly where they converge. What a flattened log hides, the lattice draws.
A quiet navigator for git history
Lattice draws your repository's commit graph as it actually happened: parallel lines of work keep their lanes, merges converge in the open, and the diff is never more than a keystroke away.
curl -fsSL get.lattice.sh | sh
Meet the keys
macOS · Linux · WSL2 · one 1.2 MB binary, no daemon, no config
~/relay$lattice
A 128-commit history in three lanes, drawn and laid out in 4 ms.
A log flattens history.
A lattice keeps the shape.
Why lattice
History is not a list. It is a set of lines running in parallel, diverging and converging. Lattice draws that structure, then lets you move through it.
Every commit sits where it actually happened. Parallel lines of work keep their lanes, and merges converge exactly where they converge. What a flattened log hides, the lattice draws.
j and k walk the history, g and G jump to the edges, t opens a commit in your editor, and / filters by hash, author, or message. Nothing to click, nothing to configure.
o opens the diff, s opens the file as it was at that revision, y puts the hash on the clipboard. The answer is never more than a keypress from the question.
The keys
Every binding works out of the box. If you rebind one, .latticerc is three lines long.
Install
curl -fsSL get.lattice.sh | sh
brew install lattice works too, if your tools live in Homebrew.~/.local/bin.lattice --uninstall. Nothing else is left behind.macOS 12+ · Linux glibc 2.31+ · WSL2 · x86_64 and arm64