ctxfs Get in touch

Prototype · Developer tooling

ctxfs

Run twenty agents against one repository without any of them seeing another one’s mess.

Anyone whose parallel-agent experiment died on the second `git checkout`.

Animated illustration of ctxfs ctxfs — session $ ctxfs run --scope . resolving workspace … Rust indexed 1,284 files · 96 changed analysis complete — 4 findings, 0 blocking $ ctxfs report --format=json written to ./report.json UNCHECKED UNWRAP IN RETRY PATH src/net DUPLICATE CONFIG PARSE src/cli DEAD BRANCH AFTER EARLY RETURN src/store TEST ASSERTS ON FORMATTING tests
Animated schematic of a representative session. Command names are real; timings are compressed for the page.
Built on
Rust + Windows filesystem APIs
Fits the workflow
A step in the pipeline, not a replacement for it
History
66 commits, in a private repository

What it is

Running N coding agents against one repository on Windows normally means N full working copies. ctxfs gives each agent a private, writable view of the same repository instead: reads fall through to a shared read-only base snapshot, and writes are captured copy-on-write into a per-context upper layer.

Each context is a real git repository, so work is reconciled back through ordinary git merges rather than a bespoke sync protocol. The base is pinned at one commit and is never written to.

Capabilities

What it actually does.

Anyone whose parallel-agent experiment died on the second `git checkout`.

  1. Shared read-only base snapshot

    Shared read-only base snapshot with per-context copy-on-write upper layers

  2. Every context is

    Every context is a real git repository — reconciliation is a normal merge

  3. Passthrough, overlay

    Passthrough, overlay, git lifecycle and hardening milestones complete

  4. End-to-end acceptance demonstration

    End-to-end acceptance demonstration passing against the specification

How it works

3 moves, end to end.

This is how ctxfs works, not a set of steps you can follow yet — it is prototype and not distributed.

  1. Drop it in

    ctxfs attaches to the repository or project you already have.

  2. Give it the job

    It takes a concrete task with a defined output, not an open-ended prompt.

  3. Review the result

    Everything it produces is a diff, a file or a report you approve before it counts.

The full technical description

Specification

Made of, and made when.

Read from the repository at build time rather than typed onto a marketing page.

State
Prototype
Discipline
Developer tooling
Shape
Developer tooling
Started
Jul 2026
Last change
Jul 2026
Commits
66
  • Rust
  • Windows filesystem APIs
  • git

Next

Put ctxfs in your pipeline

Ask about integrating it with the repositories and agents you already run.

This is a pre-production site. All content is subject to finalisation, and nothing stated here is binding until the site is live.