Comparison · Jujutsu

Jujutsu vs Git vs TOVIO

Jujutsu (jj) is a Git-compatible version control system that treats the working copy as a change, records every operation in an undoable log, and stores conflicts as data. Here is how it compares with Git and with TOVIO's design, row by row.

How to read this

native / first-class partial or workaround not supported

Jujutsu and Git cells reflect a 2026 snapshot of each tool's publicly documented behavior and will change as those projects evolve; where another system genuinely leads a row, the table shows it. TOVIO cells reflect the v1 design target — TOVIO is pre-1.0, unpublished, and not yet independently audited. See the launch gates and what ships today for current implementation status.

Against the systems reinventing the model

$against the systems reinventing the model2026 snapshot · TOVIO = v1 design target
CapabilityJujutsuGitTOVIO
Offline-first, fully distributedNative or first-classNative or first-classNative or first-class
Per-file cryptographic permissionsNot supportedNot supportedNative or first-class
AI-agent capability tokensNot supportedNot supportedNative or first-class
Agent commit provenanceNot supportedNot supportedNative or first-class
Change-centric identity (survives rebase)Native or first-classNot supportedNative or first-class
First-class conflict objectsNative or first-classNot supportedNative or first-class
No staging areaNative or first-classNot supportedNative or first-class
Binary parity (no LFS bolt-on)Not supportedNot supportedNative or first-class
BLAKE3 content addressingNot supportedNot supportedNative or first-class
Lane pointers auto-reconcile when offline copies divergeNot supportedNot supportedNative or first-class
Full operation log / undo-anythingNative or first-classPartial or workaroundNative or first-class
Semantic diffs & behavioral versioningNot supportedNot supportedNative or first-class
Open specification, no vendor lock-inNative or first-classNative or first-classNative or first-class

What the rows say

Where Jujutsu is native today

  • Offline-first, fully distributed — also a TOVIO v1 design target
  • Change-centric identity (survives rebase) — also a TOVIO v1 design target
  • First-class conflict objects — also a TOVIO v1 design target
  • No staging area — also a TOVIO v1 design target
  • Full operation log / undo-anything — also a TOVIO v1 design target
  • Open specification, no vendor lock-in — also a TOVIO v1 design target

What TOVIO's design adds

  • Per-file cryptographic permissions — not supported in Jujutsu
  • AI-agent capability tokens — not supported in Jujutsu
  • Agent commit provenance — not supported in Jujutsu
  • Binary parity (no LFS bolt-on) — not supported in Jujutsu
  • BLAKE3 content addressing — not supported in Jujutsu
  • Lane pointers auto-reconcile when offline copies diverge — not supported in Jujutsu
  • Semantic diffs & behavioral versioning — not supported in Jujutsu

More comparisons