Chapter 10 — Launch the Bench and Verify Capture
Bench — the live dashboard
From a run directory:
cd /path/to/your/run-dir
iris
Or point to it explicitly:
iris /path/to/your/run-dir
The launcher prints the reachable address, verifies startup, and normally
backgrounds the Bench so your terminal can return. A failure stays visible
instead of reporting a successful background launch. iris-bench.log in
the separate Bench store records the address and server messages.
Launch options
--no-openor--no-browsersuppresses automatic browser opening.--port Nselects a preferred port; check the actual address printed.-for--foregroundkeeps the process attached to the terminal.--replayloops a recorded run over a virtual clock for demonstration.
The Bench can attach to a live run, open a completed bundle, or show a Navigator when a directory has no run artifacts. When several bundles are present without a live writer, the startup banner identifies the selected one. Check that identity before interpreting charts.
Find or stop an existing Bench
iris open
iris stop /path/to/your/run-dir
iris open opens tabs for registered Benches on the machine. iris stop
stops the Bench associated with a directory; it does not stop the training
job. The browser dashboard's restart control similarly restarts the Bench,
not training. A directory's index.html can redirect to its running Bench.
Verify capture before interpretation
Check the run name, model identity, captured-step range, probe domains, and frame count. Read unavailable-channel messages and sampling gaps. Pending analysis is different from a channel the run never recorded.
Use Export as PDF to generate a report from the captured bundle. Read and review an export before sharing it: it can contain run labels, probe content or references, measurements, notes, and trainer-supplied signals. The Bench's AI export is intended for evidence-aware discussion, not an automatic verdict about what the model learned.
Automatic shutdown
After a Bench has been used, it normally stops about a minute after the last
viewer or other keeper is gone. A browser viewer, MCP connection, enabled
MCP switch, or --keep-alive keeps it running. --no-open only suppresses
browser opening. A Bench nobody has opened yet does not time out. Restart
with iris when needed; the captured bundle remains intact.
Remote access
The Bench binds network interfaces and has no login. A printed address is not an access-control guarantee. Use a trusted network and an appropriate encrypted access path. Tailscale names are supported; follow Artifacts, Reports, Export, and Security before exposing a Bench outside your own machine.
For control actions, open localhost on the Bench machine, or forward the
port through that machine's own SSH server as your login account:
ssh -L 8765:localhost:8765 you@your-machine
Then open http://localhost:8765/, substituting the actual Bench port.
Tailscale SSH forwarding is viewing-only; use the machine's own SSH server
where supported. Opening the shareable machine hostname, even from that
machine, also gives viewing-only access. Follow the Bench's Viewing only
message for the supported reconnection method.
