The board
A local web page, on 127.0.0.1 only, that reads every watched loop's files on each request. It keeps no state of its own besides its key and the records of what it started.

The pictures on this page show invented loops.
Pages
- Loops. Every loop, grouped by repository, with status, rounds against the cap, the latest rounds as a strip, open findings, time and cost. Filter by text or status; finished loops fold away. The "Waiting for you" tab holds every question, with buttons where the loop offers options.
- One loop, in tabs, each with its own address:
- Overview: key figures, bars against the caps, a line per measure ("is it converging"), signs of no progress, the steering card, the brief and the graph of a round.
- Rounds: every round against every step; the round you pick, with each step's summary, findings, cost, retries, errors and file.
- Open findings: what the last reviewed round left open.
- Items: what the loop evaluates, item by kind of check.
- What you sent: every inbox line, whether the loop took it, and whether this board wrote it.
- Connect a loop. The two prompts, the standard, and the MCP line for the agent you pick.


Where to look first
- The tiles at the top count what waits for your answer, what runs, and what stalled or failed; a tile takes colour only when its count is not zero.
- Every row carries a stripe in its status colour, and a row that needs you (a question, a failure) is tinted.
- Beside the round count, a square per round: darker for more findings left open, a green dot for none, a ring while it runs.
Steering
- Answer or note. Appends a signed
replyto the loop'sinbox.jsonl; the loop reads it at its next round. - Stop. Appends a signed
stop; the loop finishes its round and ends. Offered only where the loop may still start a round. - Start. Runs the
commands.startthe loop's ownloop.jsonnames, in its repository, without a shell, with onlyPATH,HOME,LANGandTERMfrom the board's environment, andLOOPCAPTAIN_INBOX_KEYsaying where the board's keys are; the loop reads the key of its own folder there and is handed none. The first start of a command for a loop asks for a tick, and the page says when a script the command names changed since the board last started it. - End the process now. Only for a process the board started.
Statuses
new, running, sleeping (said when it is back), stalled (a round
went silent), waiting (for you), idle, done, stopped, capped,
failed. Status is derived from the lines on every request, never stored.