Teams running multiple agents concurrently
Safe multi-agent workspaces
Run several agents in parallel, each in its own forked vault, with atomic transactions preventing races when they share a backend.
The problem
Multiple agents working in one shared directory step on each other — concurrent writes race, and one agent can clobber another's state.
How agentvfs helps
Give each agent its own forked vault. SQLite mutations use BEGIN IMMEDIATE / COMMIT / ROLLBACK, and a weak-reference cache keeps one backend handle per vault, so concurrent access stays consistent.
What that looks like in practice
- ▸One forked vault per agent isolates workspaces cleanly.
- ▸Atomic SQLite transactions eliminate concurrent-write races.
- ▸Backend deduplication prevents resource leaks under concurrency.
- ▸Per-vault quotas stop any single agent from exhausting disk.
Try it on this workflow
See the architecture, more use cases, or the guides.