[brainit-consulting]

Coders can work in their own Upstash Box: a Linux machine in the cloud, signed in once to the Overlord's own Claude or Codex subscription, with its own clone of the repo. It takes builds, tests and the test browser off this computer. Testers stay local.

What's in it

• Box layer (server/boxes.ts): the Box API through @upstash/box; key from UPSTASH_BOX_API_KEY, a shared fine-grained GitHub token from CODEDUNGEON_BOX_GITHUB_TOKEN (env or the Windows user environment, never written to a file or the box's disk); a base snapshot with tmux, the Playwright MCP and its Chromium, no logins.
• CLI in a box (server/boxRunner.ts): BoxPty implements Pty. The CLI runs in tmux; the dungeon's terminal is tmux attach over a PTY session that reconnects; hooks write to an events file the dungeon follows with tail -F.
• Guild → Works on (🖥 This PC / ☁ Upstash Box), Sign in the box (the CLI's own sign-in in their terminal), and a Cloud boxes card in Settings (enable, limit, Build the base box, CPU used against the free plan's 5 h).
• Guide chapter III, how-it-works and the code map describe it.

Measured in the test dungeon (Captain Pickle, port 4470)

• Issues 96, 98, 100, 102, 104, 106 done by a coder in a box → PRs 97, 99, 101, 103, 105, 107, tested by the local tester and merged.
• The browser tool in a box: screenshots on a phone held sideways and upright (PR 99).
• Crash mid-task and restart: the coder resumes in the box with the desk as it was and finishes (PR 105). Ctrl+C mid-task: nothing left running in the box; on start the coder resumes and finishes (PR 107).
• Leftover CLIs from earlier restarts are stopped when the next one starts (pkill -x tmux matched nothing: tmux's server is named "tmux: server").

Known limits

• Box CLIs aren't held by the terminal keeper: a restart replays the turn in progress from the transcript.
• No token metering or browser screenshots collected from boxes; cost comes from the status line.
• Linked repositories aren't in boxes.

🤖 Generated with Claude Code