Purpose
Tauri desktop browser with agent, browser, DNS, files, node, spaces, and wallet commands. This page follows the real source shape for Dbrowser 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
AgentAction— tools/dbrowser/src-tauri/src/commands/agent.rsAgentMessage— tools/dbrowser/src-tauri/src/commands/agent.rsAgentResponse— tools/dbrowser/src-tauri/src/commands/agent.rsAgentStatus— tools/dbrowser/src-tauri/src/commands/agent.rsAppState— tools/dbrowser/src-tauri/src/state.rsAuditLog— tools/dbrowser/src-tauri/src/commands/agent.rsAuditRecord— tools/dbrowser/src-tauri/src/commands/agent.rsChainBalance— tools/dbrowser/src-tauri/src/commands/wallet.rsDnsRecord— tools/dbrowser/src-tauri/src/commands/dns.rsDomainLookup— tools/dbrowser/src-tauri/src/commands/dns.rsDomainSearchResult— tools/dbrowser/src-tauri/src/commands/dns.rsFileEntry— tools/dbrowser/src-tauri/src/commands/files.rs
Example shape
Release-quality documentation checklist
- Every public type on the API Surface page has at least one sentence of behavior documentation.
- Every fallible operation lists errors and recovery guidance.
- Every networked example names the peer/session/topic lifecycle.
- Every storage example names durability, repair, and deletion semantics.