Code Dungeon · The User Guide

Chapter I

The dungeon and how it is laid out

Code Dungeon is a real software workshop drawn as a dungeon. Every coder you see is a real coding agent working on one of your GitHub repos, and everything they do (issues, branches, pull requests, test reports) is real. The dungeon is one level: a great hall, a gallery running south from it, and a chamber for each project.

The great hall

You start in the great hall. Its corners and walls hold everything that is about the whole dungeon rather than one project:

  • Your study, the room at the back left. Your table is there: press E at it to open the Overlord's ledger (chapter VI).
  • The DungeonMaster's quarters, at the back right under the DUNGEONMASTER sign. Press E on his bench to see what he is working on.
  • The bar, in the middle of the hall, with kegs and bottles behind it. The cat likes to sit on it.
  • The hearth and two feasting tables, towards the south end.
  • The recruits' chairs along the east wall. Anyone the DungeonMaster wants to recruit waits here for your decision.
  • The dart board, on the south wall at the west end (chapter VII).

The archway in the middle of the south wall leads into the gallery. Every connected repo has its own chamber off the gallery, alternating west and east. A chamber keeps its number for as long as its repo is connected, so removing one project never moves the others.

Each chamber has a pair of oak doors. They creak open as you come up the gallery towards them and swing shut once you are well past, so from inside one chamber you see the shut doors of the chamber opposite.

The Roll of Chambers beside the archway lists every chamber: press E on it to walk straight into one instead of finding the door.

Inside a chamber

  • The notice board on the far wall, facing you as you come in: the chamber's issues and pull requests (chapter IV).
  • The coders' workbenches, each with a slate on an easel showing that coder's live terminal (chapter V). While they work they write in the ledger on their bench, the quill pinched between thumb and forefinger. The ink goes down as they write, laid out like code, they dip in the inkwell now and then, and turn the page when it's full.
  • The assay room: the testers in aprons along the east wall, who check every pull request before it is merged.
  • The gauges on the far wall, right of the SHIP IT sign: how hard this computer is working (processor, memory, disk) and how Claude usage stands. Press E on them for the full readout, refreshed every five seconds. The bottom line, Today at API prices, adds up every session since midnight: the tokens, and what they would cost at API list prices. A subscription doesn't charge by the token, so this isn't what you pay; it shows how much work went through. Codex and OpenCode report no figures, so their sessions aren't in it.
  • The framed screen on the left wall: the project's own app. Press E on it and the app starts by itself on the default branch, and you use it right there. You can switch it to any open pull request. If you press Stop, it stays stopped the next time you open the screen, until you start it again.

The plate at the top left of the screen always tells you where you are: the chamber number and repo name, or G and the great hall, with how many people are in the guild, how many are working, and how many pull requests are in QA or ready to merge.