Install
- Download for Windows or macOS.
- Setup finds Claude Code, Codex and OpenCode by itself.
- Hooks are run by Node, so Node must be on the machine.
- Hooks are silent and always exit 0. They cannot end a turn.
Sign in
- Continue with GitHub, Google or Microsoft. Any mix a hub turns on.
- Or an invite key: one use, 14 days.
- On an unclaimed hub the first sign-in becomes the owner.
- A second account links to the same person by verified email.
Team
- The owner invites by email or GitHub login. The invite carries a key.
- The board shows who is prompting what, and which files each agent touches.
- Two people about to edit one file get a warning.
- Paths are relative to the repo, so Windows and macOS teammates collide correctly.
- The hub is one Node process with no dependencies. Run your own.
Steer
- Steer on a teammate’s agent row aims your composer at it.
- It arrives as a turn starting [from you]. Text only.
- Run as, or + agent on a teammate’s machine, starts a new agent in their app.
- The owner sets one team policy: Ask first, Always on, Always off.
- Ask first shows them a card. Nothing reaches the agent until they approve.
- Only agents running in the Zevet app can be steered.
Shared editing
- Open a workspace, click a file. Teammates’ cursors are in it.
- Your agent’s edits appear as they land on disk.
- Only files people have opened are shared. Git is untouched.
- A file too large to share opens read-only.
How the encryption works
- The team shares one secret.
- The auth token is SHA-256 of the secret. The document key is HKDF of it.
- Each update is AES-256-GCM, with the room name as additional data.
- The hub relays ciphertext.
- What that does and does not cover is on the security page.