TUI

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

# Launch the curses TUI against the currently running node.
weave tui

# Connect to a remote node (read-only) over the JSON-RPC endpoint.
weave tui --endpoint http://198.51.100.7:4042/rpc --read-only

# Boot the daemon and the TUI in the same shell using job control.
weave daemon --listen /ip4/0.0.0.0/udp/4040/quic &
sleep 1
weave tui
fg %1   # bring the daemon back to the foreground when done

# Keybindings inside the TUI:
#   p      switch to peers pane
#   s      switch to strands pane
#   l      switch to locus drives pane
#   /      filter rows by substring
#   q      quit