$ ctxfs roadmap
What’s planned
Where ctxfs stands today, what’s scheduled next, and what it isn’t going to do.
Where it stands
All four planned milestones are done.
Passthrough, the copy-on-write overlay, the git lifecycle and the hardening pass each had an acceptance suite that had to pass before the next one started. Per-process divergent views were added behind an experimental flag. The open question now is portability.
Planned work
What’s being built
Grouped by theme, in the order we plan to do them. There are no dates, and nothing on this page is a delivery commitment. The order can change if a customer gives us a good reason.
-
Under consideration
A Linux backend
ctxfs runs on Windows filesystem APIs today. A Linux backend using libfuse is designed but not implemented, and the specification lists it as optional. The holdup is testing: it could be written on the current setup but not verified there, and this project’s rule is that each gate passes before the next thing starts. We’re not going to ship a filesystem backend nobody has mount-tested.
- A libfuse backend behind a build tag, once there’s an environment that can verify it
- The same copy-on-write and git-reconciliation semantics, checked by the existing acceptance suite
Out of scope
Not on the roadmap
If you need one of these, ctxfs isn’t the right product for you.
-
A sync protocol of its own
Every context is a regular git repository, so reconciling is an ordinary merge. A custom sync layer would be one more thing to trust.
-
Writing to the base snapshot
The base is pinned to one commit and never written to, which is why you can throw a context away.
-
Running the agents
ctxfs gives an agent a private view of a repository. What runs in that view is up to you (or Agent Lab).
How this is maintained
Every item above is tracked in our own issue tracker, and this page is rewritten from it. Open bugs and security work are left off. Those stay in the tracker until they’re closed.
Want more detail on something here, or to know where it stands? Write to dmoore@
Next
Put ctxfs in your pipeline
Ask about hooking it up to the repositories and agents you already run.