AgentFS and Mirror

Purpose

Main Weave CLI and TUI covering strand, dSocial, Locus, Lens, Nexus, DHT, AgentFS, mirror, config, forum, gnosis, and basis commands.

This page follows the real source shape for Weave and explains the workflow a developer is likely to use first.

Developer workflow

Start from the smallest constructor or builder, perform one meaningful operation, inspect the returned state, then add the relevant policy, storage, or network integration. The examples below should be expanded whenever the crate API changes.

Primary types to know

• App — tools/weave/src/tui/app.rs
• Cli — tools/weave/src/cli.rs
• NetworkConfig — tools/weave/src/config.rs
• PeerInfo — tools/weave/src/tui/app.rs
• StorageConfig — tools/weave/src/config.rs
• TuiConfig — tools/weave/src/config.rs
• WeaveConfig — tools/weave/src/config.rs
• AgentFsCommand — tools/weave/src/cli.rs
• BasisCommand — tools/weave/src/cli.rs
• Command — tools/weave/src/cli.rs
• ConfigCommand — tools/weave/src/cli.rs
• DhtCommand — tools/weave/src/cli.rs

Example shape

# 'weave agentfs' wires the local AgentFS to a Locus drive and 'weave mirror'
# drives content-addressed mirroring against a remote peer.

# Initialize the on-disk AgentFS root for an agent identity.
weave agentfs init --root ~/agentfs/ops-bot --identity did:l1fe:agent:ops-bot

# Pair it with a Locus drive so files are content-addressed onto the strand.
weave agentfs link --root ~/agentfs/ops-bot --drive workspace

# Mirror an upstream drive into the local Locus, applying NewerWins on conflict.
weave mirror sync workspace \
  --from did:l1fe:agent:upstream \
  --conflict newer-wins \
  --dry-run

# Watch mode keeps the mirror live until interrupted.
weave mirror watch workspace --debounce-ms 250 --include "**/*.md"

# Inspect the last sync report.
weave mirror status workspace