Near-free parallelism for your agents.
AgentFS gives you near-free parallelism. Spin up as many workspaces as you have agents — each is a full, warm, isolated copy of the project in well under a second, nothing is cloned or copied — and land the results one at a time with every write attributed and no merge surprises. The directory is still just a directory: same path, git works, caches warm.
cargo build --release in a fresh forkMeasured 2026-08-16 on the Wigwam repo itself (2,857 tracked files, btrfs).
What a parallel attempt costs
| everything else | AgentFS | |
|---|---|---|
| Create | clone / git worktree add / copy the tree — seconds to minutes, disk × N | afs new <task>: store-backed mount, sub-second, no bytes copied |
| Warm-up | cold target/, node_modules/, .venv per copy — first build costs minutes × N | build caches are copy-on-write clones of a warm seed; first build is incremental |
| Agent state | new path ⇒ Claude Code memory and sessions keyed on cwd are blank | forks inherit the parent's memory — an agent starts warm |
| Isolation | shared dir ⇒ agents trample; containers ⇒ copy the world, no history | each workspace is its own overlay; shared workspaces still attribute per writer |
| Merge | git merge / manual diff — nobody knows which attempt wrote what | afs land; a bounced land is a structured refusal → replay (auto when disjoint) → reconcile in a merge workspace, never a silent merge |
| Audit | archaeology — git blame after the fact, if it was ever committed | every write attributed at write time: afs ops, afs blame |
| Undo / exit | delete the clone and hope | afs rm (history stays); an adopted repo restores byte-for-byte |
Your repo is still just a directory
Adopt = rename your directory aside and overlay the store on it — nothing copied. Unmount = write the tree back, rename it home. There is no third bucket a file can fall into. Click any part to learn more.
Is my repo safe?
Does git still work?
Yes, natively. Inside the mount .git is a gitfile pointing
at your real git directory — the mechanism git itself uses for
worktrees. status, commit, pull, rebase, hooks: unchanged, and never routed through FUSE.
Can I undo it?
afs unmount restores the plain directory: the store's
tracked files are written back over the origin and it is renamed to
the original path — byte-for-byte what you would have had, plus your
edits. Nothing is ever deleted; afs rm on an adopted repo
only deregisters it.
What is not captured?
Whatever git ignores. .env, secrets, local settings,
build output live in the origin and are served straight through:
present in the tree, never captured, never replicated, never leave
the machine. Same tracked/ignored line you already know from git.
How parallel agents work
afs new <task>— one workspace per independent task. It mounts in under a second with warm caches and the parent's agent memory.- The agent works in it like any directory: reads, edits, builds and tests
through the workspace entrance (
afs run <task> -- cargo test). Every write is captured and attributed as it happens. afs stage -m "…"checkpoints the result as an immutable snapshot and prints its id. Workers stop there.- You land snapshots onto the branch one at a time:
afs land. Head moved?afs replayrebases and lands automatically when the paths are disjoint. Overlap?afs reconcileprepares a merge workspace you build, test, and land. Nothing merges silently.
Two histories, one tree
Git keeps commits; the store keeps attributed snapshots. They describe the
same tree and each does its job: git for what you publish, AgentFS for who
wrote what, when, and which parallel attempt it came from. afs push fast-forwards the repo to the branch head and commits
with git; afs pull lands the repo's own captured edits. Neither
replaces the other, and neither is a copy.
Platforms
| Platform | Tier | Status |
|---|---|---|
| Linux | mounted (FUSE) — live capture, adopt in place, forks | available |
| macOS | mounted (macFUSE) — same design | available |
| macOS without macFUSE · Windows | plain adopt in place — ordinary files, checkpoint with afs stage, same land / replay / reconcile | available |
| Windows mounted (WinFsp) | mounted tier | planned |
Compared with
Git worktrees are cheap to create but cold: every one rebuilds from scratch, changes the path your tools key on, and knows nothing about who wrote what. Sandboxes, containers, cloud dev boxes copy the world per attempt — no local warmth, no history, and merging is your problem. A shared directory is free and has no isolation and no attribution: agents trample each other. AgentFS is the only one where N parallel agents cost roughly what one does.
AgentFS ships with Wigwam; the relay replicates workspaces between your machines.