Raven Teams

Signed out is the default

Signed out means the team thread never starts — Raven has no dependency on the service at all. Sign in from Settings → General → Account, and nothing about your session is published until you opt a space in.

Signing in creates a key for this device alone, kept private to your account; Raven refuses to use it if the file is ever readable by anyone else on the machine. Spaces are opted in one at a time, from the space’s own menu — until then the team can see that you exist and nothing more.

Your own remote host

Run raven-muxd on a Linux server and open its panes in Raven on your Mac through the hosted team relay. The remote-host guide walks through installation, sign-in, a persistent service, secure pairing, and opening local and remote panes together. The server needs outbound access on port 443, with no public terminal port or VPN.

Covering: a teammate answers your approvals

Covering hands your approvals to a teammate for a bounded time — up to 24 hours, four by default — and the whole team sees it in the roster. There is no secret delegation.

• They answer a blocked approval from their own window. It arrives on yours attributed to them and resolves exactly as if you had pressed the key.
• One approval, never a session grant. Covering cannot hand out standing permission.
• ask_user questions are never delegated: a coverer can unblock a tool call, not answer in your voice.
• Taking the approvals back is immediate, and does not wait for the window you granted.

The sidebar grows a third mode once you sign in to a team from Settings; before that it has only Spaces and Inbox. Team is the covering inbox: whoever you are covering leads it, so someone else’s blocked agents sit in the same list, read the same way, as your own.

Sharing a pane, by a signed word

Sharing a pane grants one teammate Watch on one pane, for a bounded time, signed by your device. Letting them type is a second, separate grant — deliberately: watch first.

When they open it, the two windows meet at a brokered edge. The pane’s bytes never touch the service. The share sees exactly one pane and cannot leak the rest of your session, and revoking it removes the row everywhere and closes the connection.

One backlog, local-first

The team’s shared backlog is the notes pane. Every surface reads the local replica, so it works offline and in any billing state, and a local edit rides an outbox to the hub and comes back as the authoritative row. Writes merge per field, so two people editing one note do not clobber each other. A purely local note the team never saw still shows up in your list.

What presence says about you

You choose how much a published space reveals. Standard carries pane titles and the name of the tool that is blocking, so a teammate can tell what they would be stepping into. Minimal reduces a title to the pane’s kind and an approval to the bare word Approval — enough to cover you, nothing about what you are working on.

Either way nothing is published until you opt a space in, and a team you have published nothing to sees only that your device is online.