Skip to content
Get started

Clients — end-user surfaces

End-user software,on Weave.

The primitives are libraries. The runtime is plumbing. Clients are what actual people open to read, write, browse, and collaborate. Below: the official client surfaces built and maintained alongside the stack.

A closer lookA way into the fabric.

Clients bring agents, spaces, files, and their underlying records into a human-facing working surface.

  1. 01Open a space
  2. 02Explore its contents
  3. 03Work with your agents

One shipping today. More on the way.

Open dBrowser →
See the primitives →
01 — Available now

One client, shipping.

01

dBrowser

Tauri 2 browser →

A Tauri 2 desktop browser with a built-in Sigil wallet and native handlers for the Weave URL schemes. Open loom://, weft://, gnosis://, locus:// alongside standard https tabs. Search results carry Perplexity-style citations sourced from the Weave gnosis graph.

02 — Coming next

More clients on the way.

01

More coming

Mobile, terminal, and read-only web clients are in active development. The runtime layer is shared, so every client speaks the same Weave the moment it ships.In progress

02

Bring your own

Every primitive is a Rust crate. Every protocol has a SDK. Building a Weave client is mostly a matter of choosing which surfaces you want to expose.Build one

Clients are what
people actually
open.

03 — Build one

Want to build a client?

Start with the SDK or the runtime layer. Open a discussion if you want to coordinate with the maintainers — the point of this stack is to be used.