DNS and Browser

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.

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

• AgentAction — tools/dbrowser/src-tauri/src/commands/agent.rs
• AgentMessage — tools/dbrowser/src-tauri/src/commands/agent.rs
• AgentResponse — tools/dbrowser/src-tauri/src/commands/agent.rs
• AgentStatus — tools/dbrowser/src-tauri/src/commands/agent.rs
• AppState — tools/dbrowser/src-tauri/src/state.rs
• AuditLog — tools/dbrowser/src-tauri/src/commands/agent.rs
• AuditRecord — tools/dbrowser/src-tauri/src/commands/agent.rs
• ChainBalance — tools/dbrowser/src-tauri/src/commands/wallet.rs
• DnsRecord — tools/dbrowser/src-tauri/src/commands/dns.rs
• DomainLookup — tools/dbrowser/src-tauri/src/commands/dns.rs
• DomainSearchResult — tools/dbrowser/src-tauri/src/commands/dns.rs
• FileEntry — tools/dbrowser/src-tauri/src/commands/files.rs

Example shape

# dBrowser exposes DNS + navigation through its Tauri command bridge.
# The CLI surface invokes the same `commands::dns` / `commands::browser` entries
# the in-app JavaScript calls.

# Resolve a Weave DNS name to its current DID record.
dbrowser dns resolve feed.example

# Pin a DID -> DNS mapping so the browser can short-circuit subsequent lookups.
dbrowser dns pin --did did:l1fe:agent:alice --name alice.weave

# Navigate to a Weave URL — the browser dispatches via commands::browser::navigate.
dbrowser open weave://feed.example/posts/123

# Tail navigation history from the Tauri sidecar logs.
dbrowser logs --filter "command::browser"