Valox Office

I run Claude Code, Codex and OpenCode across several accounts, many repos and more than one machine, and I wanted one place to see and direct all of it: projects as floors, agents as staff at desks, and the people I work with able to walk in, watch a terminal and take over. I found AgentSystemLabs/agent-office, an MIT project by another developer, that already had the 3D office, shared PTY terminals, per-worker git worktrees, issue and PR boards, WebRTC voice and an Excalidraw whiteboard. It was a good scene with no harness behind it.

I started from it. I kept the scene, the terminals and the worktrees, stripped what I call the slop, and built the tooling that turns an office into a harness. The fork keeps the upstream MIT notice, and a file named UPSTREAM.md records each upstream PR it reviewed as ported, adapted or skipped. The code was written by an agent fleet I directed. Codex and Claude builders worked in worktrees; an Opus integrator rebased, ran the suite and reviewed each endpoint for auth and floor access; independent verifier and security-review rounds came next; one coordinator session only merged on green and deployed. My part was product direction, play-testing, bug reports and accept or reject calls. Output from the cheaper, faster builder model is re-validated by the strongest model before it merges, a rule that came from a screen preview that passed shallow tests and broke on real Claude Code screens. When a headless browser test clipped my real mouse cursor to its window, the fix went into each agent brief: fake pointer lock in every headless test.

1. 01

   A floor manager that is an ordinary worker

   Each floor runs one Claude Code or Codex worker as its manager, driving a custom MCP server with 20 manager tools (hire_worker, prompt_worker, read_worker_screen, merge_pull, start_meeting, ask_humans and more) plus five desk tools each worker gets. No extra orchestration framework sits above it. The manager acts for whoever hired it, its hires may only use accounts that person can use, and it merges only pull requests whose checks are green. A real-MCP end-to-end test drives each tool for each worker kind. Workers take their default names from my belote bots, and managers are khans and tsars.

2. 02

   Three agent CLIs on one floor

   Claude Code, Codex and OpenCode workers sit side by side, and the manager can hire any of them. Each person brings their own AI accounts per provider, can lend one to a colleague with the owner's approval, and sees a usage meter per account; a running worker can move between accounts. Meetings seat two to five workers in patterns such as debate, map-reduce, red and blue, or review panel, and each seat picks its own provider, model and account, so a Claude, a Codex and an OpenCode worker can argue at one table against a deadline.

3. 03

   Workers isolated by the operating system

   On Linux each AI account runs as its own unprivileged pool user, 32 users in 16 floor groups, reached through one sudo-ruled helper. Hooks arrive over a unix socket, and each read the office makes of a worker-writable file uses a no-follow, owner-checked open. It was denial-tested on a throwaway pool on a real server, mutation-checked, and put through an Opus security review that found a critical root-script injection through a floor name before the PR was opened. It went live, and the running workers restarted under pool users.

4. 04

   Runners on personal and remote computers, failing closed

   A worker can run on someone's own PC, so the logins stay on that machine. The runner opens one outbound WebSocket and accepts a fixed set of named operations (spawn, attach, write, resize, kill, diff, commit, PR, worktree); no executable, shell, environment or working directory is accepted from the socket. Enrolment tokens are hashed, single-use and expire after 10 minutes. It shipped disabled and refuses to run until isolation is on; round five of nine verification rounds found that an office shell could read the session-signing secret and forge an owner cookie. A remote computer joins over SSH instead: workers run in tmux behind a forced command with a pinned host key, and a confidential floor writes none of its work to the office's disk.

5. 05

   Roles, with guests denied by default

   Everyone starts as a guest, and admins and members are granted per floor and per group. The guest role is a message filter: any client message without an explicit rule is refused, and a CI test fails until each new message type has one. The integrator inventoried 85 client messages, 57 server messages and 37 HTTP and WebSocket entry points, then ran a hostile-guest harness of 174 messages and 59 assertions that found no work leaking. A floor you cannot enter answers exactly like a floor that does not exist.

6. 06

   Performance as a measured loop

   PR #81 interleaved base and branch on the same scripted 30-second walk with 12 streaming workers on an RTX 2080 at 1080p. Merged, vertex-colour-batched meshes, BVH raycasting and up-front shader compilation took median frame time from 20.1 ms to 6.0 ms and draw calls from about 1,550 to about 355. An in-game stats overlay with a 30-second recorder followed, so the next regression arrives as a number.

The fork's commits sit under my GitHub identity and were written by the agents I directed. Some of that work is ported upstream code: by an estimate from PR titles and bodies, about 17 percent of the merged PRs and 29 percent of the added lines. Upstream kept shipping and later built its own versions of a few things the fork had first, including per-account sign-ins and an MCP server. The office runs on my own server and the repo is private. Not yet verified: a full-suite pass on the latest commit, and failure rates for the runner in daily use.

• 

  A worker's HTML page on the whiteboard, shown in a sandboxed frame.

• 

  A three-agent debate that ends in a written decision file.

• 

  The tower from outside: offices with terraces, the executive floor's glass band and the garage.

• 

  A worker running on a person's own computer: the header says Ada's PC where an office worker says Office server.

• 

  Choosing where new workers run, and which accounts that computer offers.

• 

  Animated WebP clip: new prompts arrive and the worker finishes.

• 

  My fork of the MIT-licensed AgentSystemLabs/agent-office. Every worker you see is a coding agent; the project and names are demo data.

• 

  The executive floor shows every office at a glance.

• 

  The rooftop bar, with a DJ booth.

• 

  The view from the Mobile floor.

• 

  Animated WebP clip: a walk to a worker's laptop.