Versioned records
Work records retain earlier versions. The event log appends, while record state, counters and locks can change in place.
Part of d0 OS · local tools in daily use
Versioned work memory for AI agents.
d0fs keeps work records across sessions. Configured hooks bring relevant file and task context into Claude Code and Codex, so an agent can pick up work with its earlier versions still visible.
Built independently by Anthony Collado. The local tools run daily on the development machine; the shared d0fs service is still in test.
The working model
Keep a usable record of the work.
The local d0fs setup gives AI agents a shared, versioned memory of files and tasks. Earlier versions are kept, and configured hook events bring the relevant records into a session.
Agent context
Hooks bring relevant records into Claude Code and Codex sessions and record configured file-edit events.
Task boundaries
The local harness refuses to start long-running jobs that nobody has declared.
Inside d0 OS
Active hooks, optional MCP tools.
The d0 OS development build includes active agent hooks and an optional d0fs MCP server with 14 tools (8 for memory and versions, 5 for tasks, 1 for pairing sessions), counted in its source and the running build on 27 September 2026. Agents can connect to that server, but it is not connected to the current Claude Code or Codex sessions; those sessions use the local hooks.
Measured in test · 27–28 September 2026
What the current build has shown.
These are development tests, not customer usage or a public service guarantee. The shared d0fs service has not replaced the daily local hooks.
The boundary
Some writes are observed later.
The hooks run at configured agent events; they do not mediate every action. Shell-based edits can be observed after the write rather than stopped before it. A separate audit ledger exists only as test code; it is not live and has no external witness.
That boundary matters. d0fs is a working tool for versioned context, not a claim that a computer or its agent sessions are tamper-proof.
Where it fits
Part of the d0 OS work.
d0fs sits beside D0 Console, the daily desktop and the alpha server in the wider d0 OS project. The shared d0fs service is in test and has not been cut over. The source repository is private, so there is no public installer today.
Introduction to d0 OSStart a conversation
Need agents to carry their work forward?
Tell Anthony what context your agents lose and what you need to inspect. Early access and research conversations are handled directly.