POSIX-like ops
POSIX-like ops compatible with the Locus API — the same calls on either side of the mirror.
Runtime 02 — Local filesystem
AgentFS. A Weave drive as a local filesystem.
Four crates that present a Weave drive as a local filesystem. POSIX-compatible operations that mirror the Locus API, debounced watchers with intelligent batching, a bi-directional sync engine, and a structured diff format for conflict resolution. Multi-device sync is demonstrated end-to-end by Loom's 7-stage integration test.
A closer lookThe fabric, in your filesystem.
A Weave drive appears as a local filesystem so existing tools and agents can work with it.
- 01Mount a drive
- 02Work with local files
- 03Keep the shared context
Four crates · POSIX-like ops · Bi-directional sync
01 — Crates
Four crates, one filesystem.
01
agentfs
POSIX-like operations over a Weave drive — open, read, write, stat.
02
agentfs-watch
Debounced filesystem watchers with batching by directory.
03
agentfs-mirror
Bi-directional sync engine between a local path and a Locus drive.
04
agentfs-diff
Structured diff format for conflict resolution and inspection.
02 — Code
Mount a drive, walk away.
use agentfs::Drive;
use agentfs_mirror::Mirror;
let drive = Drive::open("locus://team/notes").await?;
let mirror = Mirror::new("./notes", &drive).bi_directional();
mirror.start().await?; // watchers up, initial sync pass
// Now ./notes <-> locus://team/notes stay converged.03 — Capabilities
The everyday surface.
Debounced watchers
Debounced watchers with batching — bursts of edits collapse into a single sync pass.
Bi-directional sync
Bi-directional sync engine — changes propagate in both directions with last-writer-wins fallback.
Structured diff
Structured diff for conflict resolution — every divergence is inspectable, not just resolved away.
Multi-device sync
Multi-device sync demonstrated by Loom's 7-stage integration test, which runs against real DHT peers.
Everyday surface
The developer's everyday surface — most users touch Weave through AgentFS first.
Open a drive
in one line.
AgentFS is the surface most developers — and most agents — touch first. It behaves like a local filesystem and converges with the network behind the scenes.