Code Dungeon · The User Guide

Chapter V

Watching the work

Nothing in the dungeon happens out of sight. Every coder's screen is their real terminal, and you can read it, type into it or stop it at any time.

Slates

The slate on each workbench is that coder's live terminal. Walk up behind them to read it. Press E on the bench (or click it) for the full terminal, where you can:

  • click into the terminal and type, as if it were your own (while it has focus, Esc goes to the agent and interrupts its turn);
  • use the message box underneath: Enter sends, Shift + Enter starts a new line. While they work it is typed into their session; afterwards it resumes it as a follow-up;
  • press Stop to halt them, and ▶ Carry on to set them going again on the same work, where they stopped, with everything they knew. It works for coding, fixing and testing, after a Stop, after Esc in their terminal, and after their session failed or crashed. Or hand them an issue from the backlog, or Clear bench when they are done.

The top of the full terminal shows this job so far: its tokens, what they would cost at API prices, and how full the coder's context is. Hover over it to see where the tokens went: cache reads are most of them, and the cheapest.

When someone needs you

Now and then a coder or tester can't go on without you: a decision only you can make, a password or key, an account, access. They stop and say exactly what they need. It goes on your scroll with an Answer button, their panel shows needs you, and the scroll's red badge counts them until they're answered. Answer in their message box and they carry on with your answer. If you sorted it out some other way, press ▶ Carry on.

Claude Code itself sometimes stops to ask before a step, such as writing into its own settings folder or removing a folder at the top of a drive. The dungeon answers yes for you, except to a removal outside its own tmp folder: that stays for you to decide. If a coder has waited ten minutes on one, it goes on your scroll and their panel shows needs you. Open their terminal and answer it there.

Who's working

The list at the top right shows everyone working right now, with their latest thought, reply or tool call: everyone in this chamber, or everyone in the dungeon when you are in the great hall. Click a name to open their terminal. Tab shows or hides the list.

Your scroll

Press P anywhere to take out your scroll. It has three parts:

  • The DungeonMaster's letters (the first tab, under their name): write to the DungeonMaster and read what they and the dungeon send you (merges, refused merges, usage warnings). A letter can run to 20,000 characters, so a whole project brief fits; past that, the scroll says so and keeps your words until you split them.
  • Recruits: the people waiting for your yes.
  • The Realm: every project at a glance.

The red badge on the scroll counts messages and decisions waiting for you.

Sound

A handbell rings when the DungeonMaster writes to you. Bells ring when a pull request is ready to merge, fails QA or is merged, and when a new recruit arrives; a low gong sounds when someone hits an error. Quiet music plays under it all. M mutes or unmutes everything, anywhere; N turns just the music off or on. Both volumes are in the help (H).