What is planned
Where ctxfs stands today, the work that is scheduled next, and the things it is deliberately not going to do.
Where it stands
The four planned milestones are complete and gated: passthrough, the copy-on-write overlay, the git lifecycle and the hardening pass, each with an acceptance suite that had to go green before the next one started.
Per-process divergent views landed behind an experimental flag. What remains is a portability question rather than a capability one.
Planned work
What is being built
Grouped by theme and ordered by intent. These are horizons, not dates — nothing on this page is a delivery commitment, and the order can change when a customer gives us a reason to change it.
-
Under consideration
A Linux backend
ctxfs runs on Windows filesystem APIs today. A Linux backend through libfuse is designed for and deliberately not implemented — the specification calls it optional, and it is being held open for an honest reason: it can be written here but not verified here, and this project’s rule is that a gate goes green before the next thing begins. Shipping a filesystem backend nobody has mount-tested is not a trade we are willing to make.
- A libfuse backend behind a build tag, once there is an environment that can verify it
- The same copy-on-write and git-reconciliation semantics, proven by the existing acceptance suite
Out of scope
Not on the roadmap
Said plainly, because the alternative is a sales conversation that ends in disappointment. If one of these is the thing you need, ctxfs is not the product for it.
-
A sync protocol of its own
Every context is a real git repository, so reconciliation is an ordinary merge. A bespoke sync layer would be a second thing to trust.
-
Writing to the base snapshot
The base is pinned at one commit and is never written to. That is what makes a context disposable.
-
Running the agents
ctxfs gives an agent a private view of a repository. What runs in that view is Agent Lab’s problem, or your own.
How this is maintained
Every item above corresponds to work tracked in our own issue tracker, and this page is rewritten from that tracker rather than kept by hand. What is not shown: unfixed defects and security work, which belong in the tracker until they are closed, not on a product page.
Want the detail behind a line on this page, or a view of where something sits? Write to dmoore@dwmmholdings.com and ask.
Next
Put ctxfs in your pipeline
Ask about integrating it with the repositories and agents you already run.