dCLI
Usage
Using the developer browser CLI — fetch, search, perceive, and structured output for headless agent browsing.
Purpose
Developer browser CLI for fetch, search, perceive, and structured output.
This page follows the real source shape for Dcli 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
- No public items were detected by the source scan. This page should be updated when the crate exposes new items.
Example shape
# End-to-end "use dCLI to publish and replicate a signed event" walkthrough.
# 1. Initialize the node identity once per host.
dcli init l1fe ops-bot --storage ~/.dcli/ops-bot
# 2. Create the strand that will hold the events.
dcli strand create audit-log
# 3. Append an event. The CLI signs the payload with the node identity.
dcli strand append audit-log '{"kind":"login","actor":"alice"}'
# 4. Verify by reading the block back.
dcli strand get audit-log 0
# 5. Bring up the network so peers can replicate.
dcli daemon --listen /ip4/0.0.0.0/udp/4040/quic &
dcli dht announce audit-log
# 6. Tail recent events while the daemon runs.
dcli strand tail audit-log --since "10 minutes ago"