LOOM.

Workflow

The commands you'll actually use.

Snapshots with provenance, lightweight threads, semantic diffs, non-destructive undo, and a Git bridge that preserves everything. The workflow you expect — with the guarantees you deserve.

Snapshot

Capture state with intent, confidence, and full attribution.

No staging area. One command captures your working directory as an immutable, content-addressed state. Intent, confidence score, and provenance are recorded structurally — not guessed from commit messages.

Threads

Named pointers into the state graph. Not workspaces — just refs.

A thread is a lightweight reference that advances as you snapshot. Fork from any point, switch instantly, merge when ready. Threads track lineage in the DAG — worktrees provide the isolated filesystem. The distinction matters: many threads can exist without any extra disk.

Diff & compare

Semantic-aware diffs. Stat summaries. Name-only mode for scripts.

Compare any two states with structural understanding. Use --stat for a quick summary, --name-only for scripting, or --semantic for diffs that respect code structure rather than line numbers.

Undo & redo

Walk backward through any sequence of states. Preview before applying.

Undo is not destructive — it creates a new state that reverses the previous one. Preview what will change before committing. Redo walks forward again. The history remains intact throughout.

Bridge

Bidirectional Git sync. Import history, export threads, keep both worlds.

Bring existing Git repositories into Loom with full history preservation. Export threads back to Git branches. Round-trip fidelity means you adopt Loom incrementally without abandoning your current toolchain.

Built for the terminal

Shell completion, JSON output, scriptable by default.

Every command supports --json for machine-readable output. Shell completions for bash, zsh, and fish install in one step. Build automation pipelines that read Loom state as structured data — not parsed text.