A copy of the repo for each task
- Each task, worker, reviewer and the PM works in a git worktree on a branch of its own. Your own folder does not change.
- Each task gets a stub
.env: placeholder values, no real keys, and ports of its own from 41000 to 41999. A name that looks like a key, such as one withTOKEN,SECRETorAPI_KEYin it, always gets a stub. No value from your own.envis copied.
Only your computer drives the room
The routes that can run commands, such as the Claude Code panel, the Board, Tasks and Update, answer only the room page on your computer: fromlocalhost, 127.0.0.1 or [::1], from the relay’s own page, with the key. A tunnel, another website or another computer gets 403, even with the key.
The relay takes its key out of its own environment when it starts, so no session, git or gh it runs inherits the key.
Session tokens
Each session the room starts gets a token, and the token reaches only what its role needs:- Most tokens list and file tickets and use the chat board.
- The COO’s and the security officer’s only read tickets and send their report.
- A reviewer’s also posts its verdict. The PM’s and the Lead’s also edit tickets and make proposals.
- The Lead’s also reads the Floor and marks a pull request ready, and does what else you let it do.
Code or brief
Limits
The relay has no general rate limit. A session’s chat posts must be 5 seconds apart on a ticket’s channel, or 60 seconds on a fun channel, and a session files no ticket while Triage holds 20. Each answers 429 past its limit.Game seats
The room can play a game from another repo, with a session in each seat. On macOS, each seat’sclaude runs inside sandbox-exec. A seat cannot read the games, the relay’s state, or the other seats’ folders and transcripts. Where sandbox-exec is missing, a round is refused unless you turn the boundary off.
For the full rules, see Guards at each boundary and What a session’s token reaches in the technical manual.