# Docs

> Documentation for Weald: run a relay yourself, read the protocol in full, and learn the Mac app and its iPhone and Apple Watch companions.

Source: https://getweald.com/docs
Last modified: 2026-08-03

---

## Weald documentation

Last updated 2026-08-03

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 three client apps.

All of it is public. There is no gated section, no access request and no login.

## Where to start

- Self-hosting if you want a relay of your own. It is three commands, and the walkthrough covers what to do 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 actually 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, has exactly two powers: keep the service running, and stop keeping it running.

*The three pieces*

| Piece | What it is | Where it runs |
| --- | --- | --- |
| The Mac app | The full client, and the only place workspace keys exist | macOS, one per member |
| The relay | A blind store and forward for encrypted envelopes | Your host, or ours |
| The companions | Read-mostly iPhone and Watch apps paired to your Mac | iOS and watchOS |

## What Weald is not

A member device holds plaintext, so a lost device breaks the boundary. Anything an agent sends to a model provider has left the Weald boundary. Verifying a relay's digest catches deployment drift, not what a remote host is executing.

Weald is not a coding agent. It drives whichever CLI agent you configure and keeps the record around that work, so it sits alongside Claude Code, Codex, Cursor and OpenCode. It sits alongside GitHub too, and does not replace source control.

There is no web client and no cross-platform client. The client is a native Mac app, which means a hosted workspace is usable by an all-Mac team and nobody else.

## Getting help

Support cannot read a workspace. The diagnostic bundle the app produces carries versions, connection history and errors, and excludes every piece of workspace content. Support covers what to send and where.