Weald documentation
Last updated
Weald is a private workspace where a team and its coding agents keep one project record: messages, tickets, decisions and agent sessions. Content is encrypted on member devices, and the relay that carries it holds no key. This documentation covers running that relay yourself, the protocol it speaks, and the client apps.
All of it is public, with no gated section, access request or login.
Where to start
- Self-hosting if you want a relay of your own. Install is three commands, and the walkthrough covers the steps before and after them.
- Weald Protocol if you are implementing against the wire or auditing it. The specification set is published in full, with a manifest of SHA-256 digests.
- The apps if you have a relay and want to know what the Mac app, the iPhone companion and the Watch app do.
- Common questions for short answers about cost, encryption and what a relay operator can see.
What Weald is
A workspace is the encrypted record around a piece of work. It holds channels, tickets, board state, plans and the evidence a coding agent left behind, and every member device holds a full copy. The relay forwards and stores encrypted envelopes between those devices.
Group encryption is MLS, RFC 9420, over a WebSocket protected by TLS. Keys are generated on member devices and never leave them. A relay operator, including us on the hosted tier, can keep the service running or stop running it, and can do nothing else.
| Piece | What it is | Where it runs |
|---|---|---|
| The Mac app | The full client, and the reference for every surface | macOS, one per member |
| The relay | A blind store and forward for encrypted envelopes | Your host, or ours |
| The mobile clients | The Android app and the iPhone, each joining a workspace on its own; the Watch stays a companion | Android, iOS and watchOS |
What Weald is not
Weald is not a coding agent. It drives whichever CLI agent you configure and keeps the record around that work, alongside Claude Code, Codex, Cursor and OpenCode. It also works alongside GitHub and does not replace source control.
There is no web client. The Mac app, the Android app and the iPhone are native, and each redeems an invite and holds its own keys. A browser cannot hold a device key the way they can.
Getting help
Support cannot read a workspace. The diagnostic bundle the app produces carries versions, connection history and errors, and excludes all workspace content. Support covers what to send and where.