Loom is a Git replacement built for continuous multi-space history. Track code, docs, design, data, configs, notes, and AI work in one local-first timeline.
Loom is not just source control. It is the versioning engine, the sync layer, and the timeline model for the whole project.
Loom versions code, docs, design, data, config, and notes in one shared model instead of forcing everything through a file-tree-only worldview.
Your full history lives locally. Hubs extend Loom for send and receive, but the product still works offline and keeps the timeline on your machine.
Loom exposes structured models for checkpoints, diffs, restore, and timeline queries so agents can work against a real versioning surface instead of shell hacks.
loom init
loom watch
loom checkpoint "before auth refactor"
loom log
loom diff
loom restore <checkpoint>
loom hub add origin https://loomhub.dev/flakerimi/my-app
loom send
loom receiveRead the product argument, core vocabulary, and the full Loom position.
Initialize Loom in a project, understand spaces, and see the local folder shape.
Use the command surface for checkpoints, streams, hubs, send, receive, and restore.
Understand the core engine, storage model, and sync boundaries before implementation.
See operations, streams, checkpoints, entities, objects, remotes, and sync state.
Review negotiate, send, receive, transport types, and hub interaction patterns.