How the room works

A loft in New York, where each developer is one of your Claude Code sessions. This page says how work moves between GitHub, the relay, the browser and the sessions. It describes the code on main as of 2026-11-04. It shows only what is built.

The map

Four places, with you at the top. The relay is the hub: it runs every Claude Code session as a child process, hears every hook, serves the page, and is the only part that talks to the page. GitHub is reached through gh and git, with your own login.

The room map You use the browser. The browser talks only to the relay. The relay runs Claude Code sessions and hears their hooks. Sessions and the relay reach GitHub through gh and git. You, the manager what to build, the quality bar, the rungs Browser office/index.html, one tab per room The 3D room (three.js)people move as hooks arrive Claude Code panel (xterm.js)one session on screen, you type in it Board, Tasks, Huddle, Org chartread and change the relay's state Review switchesthe relay keeps them and startsevery review, tab open or not Relay relay/server.js on localhost:8787 Routes, local only/terminals /tickets /tasks /floor /update Sessions: pty-bridge.pyruns claude, keeps output, types safely Tickets and tasksa task = a worktree, a branch, a worker PR watcher (pr-comments.js)about once a minute, tells the Dev The Lead, huddles, deliveriessaved messages wait until it is safe State on disk~/.office-world/ (RELAY_STATE_DIR)tickets, tasks, sessions, lead, notes Claude Code sessions one per desk, at most 9 per room Lead · PM · Devs · reviewers Each in its own checkout.worktrees/<task or review> Hooks: relay/office-hook.jsevery event, trimmed, gives upafter 1 second, always exits 0ticket.js: tickets, Lead moves GitHub your repo, through your gh login Branchesand PRs CI: pipelinelint + tests Issues as tickets (pilot, off)relay/ticket-stores/github.js opens the page, clicks, types merges PRs (or the Lead does) HTTP streams runs, types hook events push, open PRs, comment gh api
You Browser Relay Claude Code GitHub

The page never runs anything

It asks the relay. Even Refresh the Lead is a request: the relay does the typing, because only it knows whether a prompt is safe to type into.

The relay drives every session

Sessions run in the session host, which the supervisor starts. The supervisor restarts the relay after Update, and the new relay takes each session back, still running. Stop the relay and they stop, and the next start brings each back with claude --resume. See Bringing a session back.

Sessions are plain Claude Code

They get a brief typed as their first prompt, a token for ticket.js, and their own checkout. The relay's key is taken out of what they inherit.

GitHub is the outside world

Code leaves the computer only as branches and PRs. The relay reads PRs, comments and CI with gh, and writes issues only if the GitHub ticket store is on.

A ticket's life

One ticket, from idea to running code. Each step sits in the lane of whoever does it. Dashed steps are the ones a person still does, or that need a switch you turn on. The Board's side of this, column by column, is in The life of a ticket.

A ticket's life An idea becomes a ticket in Triage, you approve it, Start makes a task and a Dev session, the Dev opens a PR, an automatic reviewer posts, the relay tells the Dev, the Dev pushes fixes, a follow-up review runs, CI passes, the PR merges, and Update restarts the relay on the new code. You Lead, PM Relay, page Dev, reviewers GitHub 1. An ideayou ask the PM 2. PM filestickets, in Triage 3. Readyyou, or the Lead 4. Startyou, or the Lead 5. Taskworktree, branch,Dev, brief typed 6. Buildtests first, push,gh pr create 7. PR + CIpipeline runs 8. Review startshook gives the PR;relay starts one 9. Reviewerposts a comment,then leaves 10. Dev is toldPR watcher, linksonly, when idle 11. Fixesreplies on the PR,pushes 12. Follow-upafter the push,if ticked, max 3 13. Mergeyou, or the Lead Lead checksreview of the head,CI green, clean 14. Updatepull, restart,sessions run on mainmerge commit findings: back to 10 Dashed: done by a person, or behind a switch that starts off. Steps 3, 4 and 13 go to the Lead only because you allowed it.

What each step leans on

StepWhoWhat makes it happen
2. PM filesPM sessionPOST /tickets/ask starts the PM, which files with relay/ticket.js. New tickets land in Triage.
3. ReadyYou, or the LeadThe Board, or ticket.js move with the Lead's token, only while you allow Let the Lead move the board.
4 to 5. StartYou, or the LeadPOST /tickets/{id}/start: a git worktree in .worktrees/, a task/… branch, a worker session, and its brief, typed only once the session is ready. At most 3 tasks build at once (RELAY_WIP_LIMIT). The Lead starts only while you allow Let the Lead start tickets, within its limits.
6 to 8. PR and first reviewDev, relayAfter gh pr create, the hook sends the PR link. The relay records it on the task, and starts a reviewer in its own checkout of the PR head, while Review PRs automatically is ticked. The page need not be open.
9. Reviewer leavesRelayThe hook reports a gh pr comment or gh pr review that worked, and the relay ends that reviewer about 30 seconds after its turn.
10. Dev is toldRelayrelay/pr-comments.js checks each task's PR about once a minute. News goes to the Dev as links, never as the comment's words, and only when the Dev is idle. The task moves back to Changes requested.
12. Follow-up reviewRelayWhen a reviewed PR's latest commit on GitHub is not the one its last review read, with or without the push's hook, once the Dev's turn ends and no review of that PR is running. At most 3 automatic reviews per PR, counted by the relay. Off until you tick Review again after each push.
13. MergeYou, or the LeadThe Lead may merge only under the merge rung: a review of the current head, blocking and fix-now findings fixed, CI green, GitHub says clean, no decision left that is yours, and never a change to CLAUDE.md, the constitution or the lint rules (eslint.config.js, eslint-local.js).
14. UpdateRelaygit fetch for the relay's folder. Page-only changes fast-forward the folder and reload the page. Relay changes wait until no session is in a turn, then the folder fast-forwards and the supervisor restarts the relay, and every session runs on through it. See Update.

Hooks up, typing down

Two flows keep the room alive. Up: Claude Code tells the relay what each session is doing, through hooks. Down: the relay types into sessions, but only when it is safe. Silence never counts as idle: only a hook says a turn has ended.

Hooks up, typing down A Claude Code event runs office-hook.js, which trims it and posts it to the relay. The relay updates the session's state and passes the event to the page, where people move. When the relay types into a session it checks notSafeToType first. Claude Code office-hook.js Relay Page Up: an event UserPromptSubmit, PreToolUse,PostToolUse, Notification,Stop, SessionStart, SessionEnd trims it: first two words of acommand, short file paths, noprompts unless you ask; addspr_url, posted, pushed1 s limit, always exit 0 from this computer only;sets state: working, waiting,idle; links the PR to its task;ends a reviewer that posted;drives Refresh the Lead the person sits, types,raises a hand, or getscoffee; the monitor showsthe tool line; the page maystart a review POST stream Down: the relay types notSafeToType says no if: the session is working or waiting a brief is still owed you have text in its prompt Enter was pressed a moment ago the screen has not settled a menu or trust question shows no hook has ever been heard then it checks again before Enter briefs, saved messages,review news for the Dev,huddle questions, the stepsof Refresh the Lead typed only when it is safe your keys in the panel goto the session as you type;the relay notes text left inthe prompt

Where the hooks come from

Either installed once in ~/.claude/settings.json with npm run office:hooks, pointing at one relay and channel, or, without those, given by the relay to each session it starts with claude --settings. See Sessions from your own terminal.

Why "safe to type" matters

Text and Enter answer whatever is on screen. Typed on a guess, a message could approve a command nobody read, or be joined to what you were typing.

What the page does on its own

Nothing that moves work. The relay starts every automatic review, so they start with the tab closed. The page sends what you press and shows what the relay says.

What the hook sends

relay/office-hook.js trims each event before it leaves the machine:

FieldWhat is sent
SessionThe first 12 characters of the session id, and the name of the project folder.
TitleThe session's title, at most 60 characters. Claude Code writes it from your prompts, so it says a little about them. If you named the session with /rename, that name is the title, and it is also sent on its own as customTitle. When the newest /rename record in the transcript has no name, customTitle is sent empty. OFFICE_SHOW_TITLES=0 keeps both back: set it when you run --install, which saves it into the hook.
Skills and subagentsThe skill name, the subagent type and its short description.
FilesThe path relative to the project, at most 48 characters.
Shell commandsThe first two words of the first command, for example npm test or gh issue. No arguments.
WebThe host name of a fetched URL.
NotificationsThe message, such as "Claude needs your permission to use Bash".
Pull requestsAfter gh pr create, the PR's address and the session's folder. After a gh pr comment or gh pr review that worked, the PR's number and repo, whether it was a comment, a review, an approval or changes requested, and the comment's link. None of the command's other words.
PushesAfter a git push that may have sent commits, only that it ran. A quiet or piped push counts too. A push that sends no commits to a branch does not: see Review again after each push for which ones.
Huddle answersOnly the one line that starts with the huddle question's marker, from what Claude Code passes when a turn ends. See Ask idle workers too.
PromptsNothing, unless you set OFFICE_SHOW_PROMPTS=1. Then the first 120 characters, which go on the monitor, and are the label until the session has a title.

OFFICE_DETAIL=full sends the first line of each shell command and search queries. OFFICE_HOOK_LOG=/some/file also appends every raw event to that file, which is useful to see what Claude Code sends. Raw events can hold whole prompts and file contents.

How events become work

Each session gets a person (see which person), and each hook event moves them:

Hook eventIn the room
SessionStartA person takes the session and goes to their desk.
UserPromptSubmitThey start work.
PreToolUse for SkillThe skill goes on their monitor, and becomes their label until the session has a title.
PreToolUse for Agent (or Task)A line on their monitor.
PreToolUse for any other toolA line on their monitor. A subagent's lines start with ↳.
PostToolUseClears a raised hand. After gh pr create, links the PR on the session's task and can start an automatic review. After an automatic reviewer posts to its PR, its session ends once its turn does (see Reviewers leave). After a git push to a Dev's PR, can start another review.
PostToolUseFailureA red line on their monitor.
NotificationFor a permission prompt or a question dialog (AskUserQuestion sends the same permission_prompt), they raise a hand and the board shows "Waiting on you". The relay puts a session at a question only for these kinds of notification_type: permission_prompt and elicitation_dialog. When the event has no notification_type, the relay reads the message, and anything but "waiting for your input" or "idle" puts it at a question. Any other kind, such as auth_success, which can come in mid-turn, leaves the session as it was, so an update still waits for its turn. While they wait they stay in their chair: on their phone, swivelling, leaning back, looking around, with the hand coming back up every so often.
StopThey finish and are ready for a prompt.
SessionEndThey finish and are free for another session.

Hooks from another computer are ignored. The relay changes no state, title or message for a hook event unless it came from this computer, because that state decides when anything is typed into a session, the Lead's brief included. Hooks run on this computer and post to localhost, so nothing real is lost. The page still shows such an event. A tunnel that rewrites Host to localhost makes every request look local, so use one that passes its own hostname through.

Typing into sessions

The relay types briefs, saved messages, review news, huddle questions and the steps of Refresh the Lead. Before each one it asks notSafeToType, drawn in the figure above, and checks again right before Enter.

Saved messages (relay/delivery.js, kept in RELAY_DELIVERIES_FILE) are typed only when:

The last rule is there because a hook can come seconds after Enter, and a second message typed before it can sit unsent in the prompt while the turn counts for it. If no turn begins in that time, the next message goes in, and the check below still looks at whether the session started.

A screen with no prompt. An idle Claude Code does not draw its prompt again on its own. After a relay restart, the relay takes each running session back with the output the session host kept, and that can be only status-line updates, with no ❯ in it. Then no saved message would go in. So when a saved message waits on a session that hooks say is idle, and its screen has shown no prompt for a minute (RELAY_REDRAW_AFTER_MS), the relay makes the session draw its whole screen again. It makes the terminal one column wider, then puts the width back at the next output, as dragging the panel's edge would. The size the relay keeps for the session does not change. It does this at most once every 5 minutes for one session. If the prompt still does not show, Needs you names the message after 15 minutes.

Text of 800 bytes or more, such as a brief, goes in as one paste. Typed as plain keys, Claude Code reads a long text about 1024 bytes at a time and keeps only the last piece. Bytes count, not characters, since a letter outside plain English can take two bytes or more. This holds for every message, a session's first brief included. The Lead's brief names ticket.js by its full path, so it is longer when the checkout's folder path is long, and it still arrives whole, however long that path is.

A key you press holds typing until Enter, Ctrl+C or Ctrl+U, even if you deleted what you typed, unless a menu was up when you pressed it. The check runs right before typing. Silence never counts as idle. Saved messages survive a relay restart, and reach a session brought back with the same id once a hook has been heard from it. While an update restarts the relay, nothing is typed, and while it waits for a quiet moment, saved messages are held for a while.

A first brief. A task's brief and the Lead's brief are saved messages too. Nothing else is typed into that session before its brief. The Lead's brief counts as in once it is typed, since a Lead with no hooks reaching the relay is still briefed. A task's brief is in only once a hook says a turn began after it was typed: typed alone does not count, so the task says brief not in yet until then, and the brief stays saved until then. If the worker ends first, the brief waits for that session id: a session brought back with the same id gets it again, and Bring back on a task whose brief is not in starts the worker over and gives it the brief. A relay restart keeps it: a worker that ran on through the restart is watched again from when the brief was typed, and is not typed into twice. Like a first prompt below, a task's brief and the Lead's brief are held by an update only while the relay restarts, not while the update waits for a quiet moment. Refresh the Lead types a brief the Lead still owes at once, with the same checks.

A first prompt. A reviewer's (from Get a review too), the PM's and the COO's first prompts are first briefs too, and each is in only once a hook says a turn began after it, as for a task's brief. Until then it is saved, both as a saved message and with its session. As for a task's brief, an update holds it only while the relay restarts, not while the update waits for a quiet moment (see While an update waits). Two things differ. If its session is not ready for it within RELAY_READY_LIMIT, counted again from when a relay comes back, or the session ends while the relay runs, the relay gives up on it and writes why in its log. And the relay tries it three more times, not once, before it calls the session stuck (below), since Claude Code can drop the Enter that follows a long paste and leave the prompt in its box. A session that ran on through a relay restart is watched again from when its prompt was typed. A session nobody spoke to comes back after a stop with a new session id and a new desk, and its prompt goes with it, typed again there.

A session that does not start. After a saved message goes in, such as review news, a Lead comment or a chat mention, the relay checks that a hook says a turn began within a minute (RELAY_TOLD_CHECK_MS). If none did, it tries once more (three more times for a first prompt), when it is safe to type: Enter if the message still shows since its last Enter, or the prompt cleared with Ctrl+U and the message typed again if it does not. It does not try while a menu or question is on the screen, since Enter would answer it. If no turn begins a minute after its last try, the session is stuck. The relay stops trying and leaves it to you. It never types a message again into a session that began a turn after it.

What to do. Open its session on the Floor. Answer the menu or question, or press Enter if the message is still in its prompt. Once a hook says a turn began, it is not stuck, and the messages that waited go in. If the session does not answer, stop it and press Bring back on its task: the message is kept for that session id, so the session brought back gets it once it is idle. A reviewer, the PM or the COO stuck on its first prompt has no task to bring back, and stopping it drops the prompt, so open its session and press Enter there instead. Stuck is kept only in the relay's memory, so a relay restart forgets it (T-53).

Is a session alive. One module, relay/liveness.js, answers this for every session, from all the relay sees of it together: what its hooks last said, when it last printed, and whether its process ended. The Floor, ticket.js floor, Autopilot's stall check, the COO's stall count and huddles all ask it, and none of them reads hooks for this on its own. Its answer is one of these:

How the relay sees a job. Hooks cannot say when a command in the background ends, so the relay reads the process tree instead. Every 5 seconds the session host runs ps once and looks at the children of each session's claude process. A child is a job when it is a shell run with -c that sources Claude Code's shell snapshot (~/.claude/shell-snapshots/), which is how the Bash tool runs every command, or any shell run with -c that has run for a minute. Every other child is a helper and does not count: caffeinate, which Claude Code starts while it works, MCP servers, and hook and status line commands, which end within seconds. The host tells the relay only when a session's jobs change. A session host started before this change does not look, so its sessions are never job until you stop the relay and start it again once.

The stall time is A session is stuck after in Settings, under Work (30 minutes, RELAY_STALL_MS). Only a hook counts as progress. Claude Code's spinner and its timer keep printing while it thinks and while a long command runs, so output says only that the process is alive and drawing. Output never makes a session working. It only keeps a session whose hooks went silent from being called stuck. A quiet session may be thinking, running a long command, or sending hooks that no longer reach the relay, and the relay cannot tell which, so nothing acts on quiet by itself. A quiet session whose output stops too becomes stuck once the stall time has passed since its last output. After a relay restart, the stall time counts again from when the new relay took the session back.

What you see on the page

While a session works, its developer types at their desk with its tool calls on their monitor (edit src/cart.ts, $ npm test). When it needs your permission, they raise a hand and the tab title counts them. When its turn ends, they stretch and go back to the coffee machine, the couch, the window, the bar table or the ping pong table until you give it the next prompt. So the room replaces your terminal tabs. What each sight means for you is in How to tell what is waiting on you.

What each desk says. Under the name, each Floor row for a session the room started says:

When any desk is safe to stop, Stop all safe appears in the bar at the top of the Floor with how many. It and each Stop send POST /floor/stop, and the relay asks the same verdict again at that moment, so a desk that started working since the page drew it is not stopped. You stop them, so Let the Lead stop sessions and the Lead's hourly limit do not apply. A stopped Dev keeps its checkout and branch, its task's history says you stopped it from the Floor, and Bring back returns it. The page asks GET /floor every 3 seconds. The relay builds each desk (relay/desk.js) from what it already keeps: tasks, the pipeline it polls, automatic reviews and Autopilot's last look. Drawing a desk asks GitHub nothing, so the CI and review words are as old as the relay's last poll.

Where a label comes from. A worker on a ticket shows T-17 · its title, and a reviewer of that ticket's PR shows reviewing T-17 · its title. The relay works this out (workOf in relay/tasks.js) and sends it as work with each session in GET /terminals, so a reload loses nothing. A worker on a task with no ticket shows the task's title for as long as the task lasts. Otherwise it is the session's title: the one Claude Code writes soon after the first prompt, or your own if you run /rename building worker labels in that session. It appears on their name tag, the Floor list, the board and their monitor at their next event. Claude Code does not document where it keeps titles, so if that changes, the label falls back to the skill or the project folder.

A title you give a session. Run /rename my title in a session the room runs, and my title shows right after that person's name, as Paul · my title: on their name tag in the scene, on their row in the Floor list, and in the Claude Code panel's header when their session is open. This works for every session the room runs: one you added, a task's Dev, a reviewer, the PM, the COO and the Lead. Only a title you set counts. The one Claude Code writes by itself does not show here. The hook sends it as customTitle, and the relay keeps it with the session in sessions.json, so it is still there after the relay restarts, and sends it as customTitle with each session in GET /terminals. More than 30 characters is cut with …, and the whole title shows when you hover over it. It is shown as text, never as HTML. When the label after the name would only say the same title again, it shows the project folder instead. A new conversation in that terminal, after /clear or /resume, starts with no title until its own transcript has one. The page reads it every 2 seconds. A session from your own terminal, which the room does not run, does not show one. The person's name stays as it was everywhere a name is matched, such as an @ mention in Chat, a huddle, node relay/ticket.js stop Paul and the Floor's names.

The room looks like a loft in New York: exposed brick, steel factory windows with water towers outside, cast iron columns, ductwork, Edison bulbs, a coffee bar and a couch. People are built from spheres, cylinders and boxes on a rig of joints (pelvis, spine, neck, shoulders, elbows, hips, knees), posed by joint angles in POSE. They walk on a 15 cm grid with A*, and each plan is a list of steps: stand, walk, face, sit, act.

Guards at each boundary

What stops the room from doing what it should not.

BoundaryGuardEnforced by
Browser to relayThe terminal, Board, Tasks, checkouts and Update answer only the room page on this computer: loopback, a localhost Host, the relay's own Origin, and the key.Code (localOnly)
Session to relayA session's token lists and files tickets. The Lead's also reads the Floor. A Lead you allowed can also move the board, stop sessions and start tickets, each within its limits. Nothing else. See tokens.Code, with tests
Hook to relayEvents from another computer change no state. The hook sends trimmed fields, and prompts only if you turn that on.Code
Relay to sessionTyping waits for notSafeToType. Worker and huddle text reaches the Lead quoted as untrusted.Code, and the brief
Session to GitHubSessions run with your gh login. Briefs say never merge (except the Lead's merge rung). Nothing stops gh pr merge but the brief.The brief only
CommitsThe pre-commit secret check, which stops a commit that adds a key or password. The same hook then runs lint on the JavaScript files the commit changes, as they are in the working tree, and stops the commit when lint fails. In a worktree with no node_modules of its own, it finds ESLint in the checkout above it. With no ESLint installed, the commit goes through with a note. CI runs the same check on the lines and files a pull request adds since its base, so a commit made with --no-verify, or on a computer without the hook, still fails the pipeline check. Taking the secret out in a later commit makes the check pass, but the key stays in the branch's history, so replace it. A separate Secret scan check, on each pull request, in the weekly run and on a run you start by hand, reads every line of every tracked file in the checkout the same way, skipping binary files, so a secret already on main is found too. It also fails on a tracked .env, .env.local, .envrc or .envrc.local, but not on a .example, .sample or .template copy such as .envrc.example. GitHub does not require it unless you add it to branch protection. secret-check: allow on a line marks a false alarm in all of these, and none of them prints the value it found. CI also runs lint, the tests, and the browser tests of the room page, and GitHub requires the pipeline check on main. Lint also fails on a new comment in relay/, office/ or shared/, outside relay/test/. The comments already there are counted in eslint-suppressions.json, and the counts only go down: npm test fails when a count is higher than at the merge base with main. See README.md.Checks
Notes and memoryThe Lead's handoff notes and the PM notes grant nothing. A line that reads like a permission is confirmed with you.The brief only

The trust ladder

How much the room is trusted to do alone. The rungs come from article 5 of docs/constitution.md: each is off until you turn it on.

Step toward running aloneStateTicket
First review of every new PRonbuilt
Review findings reach the DevonT-17
Follow-up review after each push, by the relayswitch, starts offT-54
The Lead moves the boardyour switchbuilt
The Lead merges a reviewed, green PRon, by your wordT-48; a switch is T-50
The Lead knows the Floor, and who can be stoppedonT-62
The Lead stops posted reviewers and Devs whose work mergedswitch, starts offT-55, T-92, RELAY_LEAD_STOPS
Update goes back to the last good commit when the new relay failsswitch, starts offT-80, RELAY_ROLLBACK
Update goes through merges one at a time, and checks eachswitch, starts offT-81, RELAY_ROLLBACK
The Lead starts tickets, a few at a timeyour switch, with limitsT-37
The Lead starts a review of a task's PR, through the relayswitch, starts offT-98

Rungs that are not built yet are in article 5 and on the Board, not here.

Two rooms

A second room in a second tab, for a new project, with its tickets as GitHub issues. Run a second relay with its own port and its own state folder (RELAY_STATE_DIR), and, for issues, its own ticket store. A second room has the command.

Two rooms side by side Two browser tabs, each talking to its own relay on its own port. Each relay runs its own sessions in its own repo. The first keeps tickets on this computer, the second as GitHub issues in the new repo. Each session's hooks report to the relay that started it, through the address and token that relay gave the session. Tab 1localhost:8787/office/ Relay A, port 8787main checkout of 3dtickets on this computer~/.office-world/ Sessions Awork in 3d hooks to 8787 Tab 2localhost:8788/office/ Relay B, port 8788its own checkout of 3dits own state filesGitHub ticket store Sessions Bwork in the new repo hooks to 8788 GitHub your repothe room's codePRs from A the new repoPRs from Bissues = B's ticketsneeds CLAUDE.md, CI issues, through gh api Where hooks go Each relay gives the sessions it starts OFFICE_HOOK_URL, its own address, and the session's token. The hook sends there first, so sessions of relay B report to B even when the global hooks in ~/.claude/settings.json were added for relay A. A session from your own terminal has no OFFICE_HOOK_URL, and reports where the hooks' OFFICE_RELAY_URL says.

Why a second relay, not a second channel

A channel is a separate room on the same relay, but the ticket store is set once per relay. Turning on GitHub issues for one channel would turn it on for all of them.

Why a new repo

Tasks work in their ticket's repo, so the new room's branches and PRs never touch 3d. The relay's own code stays in 3d.

Costs

Up to 18 sessions on one computer, and the relay writing the new repo's issues through your gh login.

The code

Where each part lives. It uses three.js r128 from cdnjs and its OrbitControls from jsDelivr (three@0.128.0), and xterm.js for the panel.

PathWhat it is
index.htmlA page that links to the room.
shared/nav.jsThe pad for moving the view in each world. Each world attaches it to its camera controls.
shared/relay.jsConnects a world page to the relay when it is opened with ?channel=. Uses only window.run.
docs/manual/This manual.
office/index.htmlThe page and its styles.
office/help.htmlPoints to this manual, for old links.
office/roster.jsThe people and their looks. Edit this one. See Settings kept in files.
office/office.jsThe room, the people, how they walk and sit, their plans, the hook mapping and window.run.
office/seats.jsWhat a session's job does to its title.
office/figures.jsThe skeleton every person and robot is built on, the robot designs, and which edition the page shows and how it draws each desk. See Editions.
office/poses.jsThe people's poses, and the way an arm moves at a desk so a hand never passes through it.
office/holidays.jsWhich holiday the room decorates for, from the date. office/office.js builds the decorations.
office/panel.jsThe floor board, the activity feed and the controls. Uses only window.run.
office/update.jsThe Update button in the room bar, talking to relay/update.js.
office/officers.jsThe Ask the COO and Ask security buttons and their last-report buttons, on the org chart's officer cards, and the report on the Floor. The relay's side is relay/coo.js and relay/security.js.
office/chat.jsThe chat board on the page, talking to relay/chat.js.
office/desks.jsAsks the relay what each desk says, for office/panel.js to draw, and sends each Stop and Stop all safe.
office/needs-you.jsThe Needs you panel on the Floor. The relay's side is relay/needs-you.js, with the rules in relay/needs-you-plan.js.
office/huddle.jsThe Huddle buttons and the report on the Floor. The relay's side is relay/huddles.js, and relay/delivery.js saves messages until a session can safely take them.
office/orgchart.jsThe org chart, with its Officers row and Ask the PM there. Uses window.run, the office:pick event and the Add worker folder field.
office/radio-songs.jsThe radio's six records, as notes.
office/radio.jsThe radio's instruments, its worn speaker and its buttons.
office/demo-session.jsThe pretend sessions, as hook events. Used by the page and by relay/office.js.
office/tickets.jsThe Board, talking to relay/tickets.js, on the room page and in its own tab.
office/board-model.jsThe Board's columns, filter and Done list. To give a new task state a column, add it there.
office/board.htmlThe Board in its own tab. See The Board in its own tab.
office/board.css, office/tokens.cssThe Board's styles, and the page's Light and Dark colours, shared by both pages.
office/ticket-history.jsDraws who has a ticket now and who worked on it, for the Board or any other view of a ticket.
office/fold.jsFolds the room page's Activity, Board, Chat, Tasks and Games to their title, and keeps the ones you opened.
office/tasks.jsThe Tasks panel, talking to relay/tasks.js.
office/games.jsThe Games panel, talking to relay/games.js. See The Games panel.
office/reviews.jsWhich review Get a review and the automatic reviews start, their briefs, and when a push brings another review.
office/terminal.jsThe Claude Code panel: xterm.js, talking to relay/terminal.js, one session on screen at a time. Its Get a review starts a review by hand. It also fills the room bar: the Settings button, its chips and the office-wide notes.
relay/server.jsThe relay. It also serves the pages. See The relay API.
relay/supervisor.jsStarts the session host and the relay, and starts the relay again after an update.
relay/session-host.js, relay/host-link.jsThe session host, which runs the sessions' processes so a relay restart leaves them running, and the relay's side of its socket.
relay/office.jsBehind npm run office: starts the relay if needed, opens the page, and with --demo plays pretend sessions.
relay/office-hook.jsThe Claude Code hook that sends session events to the room.
relay/terminal.js, relay/pty-bridge.pyStart claude in a pseudo-terminal in the session host for the panel, on this computer only.
relay/sessions.jsBrings back, when the relay starts, every session that was running when it stopped.
relay/seats.jsWhich person each session is: the seating rules as one function.
relay/update.jsUpdate: fetches, waits for a quiet moment, then fast-forwards the folder and restarts the relay, which the supervisor starts again.
relay/tickets.jsThe rules about tickets. Starting one makes a task.
relay/ticket-history.jsEach ticket's history and who has it now, and the name the relay gave each session.
relay/ticket-stores/Where tickets are kept: local.js by default, or github.js.
relay/ticket.jsThe command sessions use to list and file tickets and to read and post on the chat board, and the Lead to read the floor and how tired it is, move tasks and tickets, start tickets, start reviews and stop sessions.
relay/tasks.jsKeeps the tasks on disk and gives each a checkout and a worker.
relay/checkouts.jsGives Add worker and automatic PR reviews their own checkouts, and takes them away.
relay/reviews.jsStarts the automatic reviews: the first one, and a follow-up after each push. Keeps their switches and each PR's count.
relay/pr-comments.jsWatches each task's PR and tells the Dev about new comments.
relay/needs-you.js, relay/needs-you-plan.jsThe one list of what needs you, for the Needs you panel.
relay/old-relays.js, relay/old-relays-plan.jsFinds other relays on the room's state folder at start, stops an old copy of this relay, and names the others in Needs you (Old relays).
relay/floor.js, relay/stop-verdict.js, relay/desk.jsWhat the Floor says about each session, whether each can be stopped, what each desk says, and the stops by the Lead and from the Floor.
relay/pm-brief.jsThe PM's brief, as plain text from the idea and its settings.
relay/pm-brief-eval.jsReruns the PM-brief eval in edd-platform after the brief changes, and keeps the change only if the eval did not get worse (The PM-brief eval).
relay/pm-notes.jsWhere each repo's PM notes are, and what the PM's brief says about them.
relay/lead-brief.js, relay/lead-refresh.jsThe Lead's brief, and the steps of Refresh the Lead: handoff notes, /clear, and the notes read back. The relay runs them.
relay/lead-tired.js, relay/status-line.jsHow tired the Lead is: the levels, and the status line of each session the room starts, which prints the level and tells the relay.
relay/coo.jsThe COO: the measures it reads, its session, and its saved reports.
relay/security.jsThe security officer: its session, its saved reports, and the check that a report holds no key.
relay/access.jsWhat access the sessions run with, by name only: the security officer's measures.
relay/session-env.jsThe environment each session gets, and the same as names only.
relay/huddles.js, relay/delivery.jsHuddles, and messages saved until a session can safely take them.
relay/chat.js, relay/chat-summary.jsThe chat board: chat channels, posts, the relay's news, the one note a mention types in, and the summary a ticket's chat channel leaves on its ticket when you delete it.
relay/test/The tests that npm test runs, including the checks on this manual.
relay/test/browser/The tests that npm run test:browser runs: the room page in a headless Chromium, against a real relay with a fake claude.