A Space is a versioned home base where your files and the workflows that run them live together — and where you and your AI crew dock to get work done. Every change is logged. Nothing drifts.
Storage just holds cargo. A base runs it. Under .capora/ live the systems — change-driven pipelines and schedules — that turn a folder of files into a station that operates itself, whether you're at the console or not.
Address it by name — remote://you/… — and it's the same base for every human and every agent who docks. Work compounds instead of scattering across machines.
Four systems keep the base alive. Compose them — the output of one is the input of the next.
Every write is a save point. Rewind, diff, and restore any moment. Content-addressed, so identical bytes are never stored — or sent — twice.
A trigger — a file change or a cron — plus one script, run in an orbital bay with your secrets. Save a file the workflow watches and it fires; the base does the work while you're away.
Claude Code rides in the runner. Have an agent edit files, review a diff, or write today's brief — then save it straight back to the base.
One base, addressed by name. People and agents dock with scoped keys, open a session so every change states its intent, and share the same files, history, and running systems.
Saving is the trigger. There is no "run it now" button — you dock the cargo, and the station takes over from a state you can point at.
Copy files up — one primitive for people and agents alike.
The write becomes an immutable save point in the base's history.
Any workflow watching that path runs in the bay with your secrets, pinned to the new save.
The run saves its output back into the base — another save point, ready for the next system.
The capora CLI is a single self-contained binary — your control console. S3-style commands you already know; a remote:// address; every write versioned and attributed to a session. Upgrades in place with capora update.
$ capora session start -m "refresh the brief" → cs_k7m2p9qx $ capora cp ./sources remote://you/data/in -m "new batch" uploaded 4 file(s) → save c_1a2f ▶ transform [on change data/in/**] queued $ capora runs transform ok 12s → data/out/brief.md transform ok 11s 2h ago
One command establishes your Space and puts capora on your PATH.