Network Commands

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.

Command surface

Use this page to understand the operational commands exposed by the tool. Prefer command groups that match the subsystem you are testing, then inspect the API surface page for the exact Rust enum or command handler.

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

# The 'weave' CLI bundles the DHT, swarm, and replication daemons so a single
# binary brings the node onto the network and keeps it in sync.

# Start the long-lived daemon (DHT + replication + mDNS).
weave daemon --listen /ip4/0.0.0.0/udp/4040/quic

# Inspect DHT peers and listeners.
weave dht peers
weave dht listeners

# Announce a strand so peers learn its discovery_key.
weave dht announce audit-log

# Resolve a peer's last advertisement and dial them.
weave dht resolve <discovery_key_hex>
weave swarm dial /ip4/198.51.100.7/udp/4040/quic/p2p/<peer_id>

# Pull a remote drive into the local Locus index.
weave locus pull workspace --from <peer_did> --discovery-key <discovery_key_hex>