Security
What the hub can read, what it does not, what is not defended.
The hub can read
- Who is editing which file in which repo, and roughly how much.
- Every teammate’s prompts. They are on the board.
- The team secret, on teams that sign in. The hub holds it on disk.
- So an operator, anyone who reads the box’s disk or memory, and anyone who ends up with a backup can decrypt document traffic.
- Everything, if the hub is taken over. The board loads its page from the hub, so a taken-over hub serves JavaScript into a window that already holds the key.
The hub process does not
- Open a document. It relays ciphertext.
- Open a steer. It relays ciphertext.
- Hold a private key for updates. They are signed elsewhere.
- Touch your git history, fork an editor, or end anyone’s turn.
“Does not” means the process never does. It does not mean it could not.
Encryption
- Each editor update is AES-256-GCM.
- The room name, repo and path, is the additional data. A relay cannot replay one file’s update into another file’s room.
- The document key is derived from the team secret.
- Steers are sealed on your machine with the document key.
Not defended
- A taken-over hub. See above.
- A hub that is only watched. Sign-in gave that up, a trade for onboarding with nothing to paste.
- Removing someone. It ends their session at once. It does not un-know a secret already on their disk. Real revocation is rotating the secret, which re-keys every document and signs everyone in again.
- Plain http. Put the hub behind HTTPS before anyone outside your LAN joins.
Not built
- Serving the editor from the desktop app instead of the hub.
- Peer-to-peer, with the code never reaching the hub.
Steer
- Text only. It cannot change a mode, grant a tool permission or answer a permit.
- One team-wide policy, set by the owner, enforced by the hub: Ask first, Always on, Always off. Default: Ask first.
- An agent started on a teammate’s machine runs in their app, their repo, their account, in their default safe mode. Three at a time.
- You see the outcome: sent, delivered, accepted, declined, refused by policy, offline.
- It is still remote prompt injection into a machine holding credentials, which is why the default asks.
On your machine
- Hooks never write to stdout and always exit 0.
- Git is untouched. Only files people have opened are shared.
- GitHub sign-in asks for a login and an id. Nothing else.
- Updates are Ed25519-signed. An unsigned feed is rejected.