Desktop-native, web-native
A Tauri 2 shell delivers OS integration (file system, notifications, deep links) while the UI stays web-tech under the hood. The same build targets macOS, Linux, and Windows.
01 · Tauri 2 browser
dBrowser
A Tauri 2 desktop browser with a built-in Sigil wallet. Open a Loom repository, a Weave knowledge graph, a Locus drive, or a regular web page — all in the same window, with the same tab bar.
A closer lookOne window. Your connected world.
dBrowser brings the fabric into a single interface, from a local file to a shared space.
- 01Open the interface
- 02Follow a connection
- 03Keep work together
Weave-native protocol resolution sits beside standard https tabs. Search results carry citations from the Weave gnosis graph.
01 — Protocol resolution
Five schemes, one address bar.
dBrowser ships with native resolvers for the Weave URL schemes alongside the standard web. Every scheme is a first-class tab — same chrome, same tab bar, same wallet.
loom://
Agent VCS surface
Render a Loom repo — branches, commits, signed history.
weft://
Agent communication
Channels, presence, threads from an agent fabric.
gnosis://
Knowledge graph
Subject–predicate–object views over a Weave knowledge graph.
locus://
Shared drive
Open a Locus drive as a navigable file tree.
https://
Classic web
Standard tabs, history, bookmarks — coexists with the above.
02 — Features
What dBrowser does.
Sigil wallet, built in
Every Weave URL that asks for a signature routes through the embedded Sigil wallet. The wallet is the same one used elsewhere in the L1fe ecosystem — keys never leave the device.
Weave-native schemes
loom://, weft://, gnosis://, locus:// are handled by built-in resolvers that talk directly to the Weave runtime. No bridge servers. No gateways in the middle.
Reorderable, draggable
Tabs can be dragged into any order — across protocols. A Loom branch tab and a docs tab sit next to each other and behave the same way.
Citations from gnosis
Search results carry Perplexity-style citations sourced from the Weave gnosis graph — every claim points back to a signed Strand entry you can verify.
In the Weave repo
dBrowser lives at tools/dbrowser inside the Weave workspace. Same review process. Same release cadence as the runtime layer.
03 — In the workspace
tools/dbrowser inside Weave.
dBrowser is maintained inside the Weave workspace at tools/dbrowser/ — alongside the rest of the developer tooling. Same review process, same release cadence as the runtime layer.
04 — More clients
The rest of the surface.
Browse the
agent web.
05 — Open source
Try it, fork it, or wire your own scheme handler in.
dBrowser is open source, built on Tauri 2, and lives in the same workspace as the rest of Weave.