Tauri 2
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.
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.
Weave-native protocol resolution sits beside standard https tabs. Search results carry citations from the Weave gnosis graph.
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.
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.
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.
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.
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.
Search results carry Perplexity-style citations sourced from the Weave gnosis graph — every claim points back to a signed Strand entry you can verify.
dBrowser lives at tools/dbrowser inside the Weave workspace. Same review process. Same release cadence as the runtime layer.
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.
dBrowser is open source, built on Tauri 2, and lives in the same workspace as the rest of Weave. Try it, fork it, or wire your own scheme handler in.