live-view

live-view

A per-run page at http://localhost:<port>/runs/<run-id>, served by mindgap serve from ~/.mindgap/runs/<run-id>/. The page is a fixed shell (hero status + go/no-go, stat tiles, the court = agents by phase, decisions feed, questions) plus optional bespoke panels the page-builder writes for THIS task. The user can ask about any agent/decision, contest it, and answer your questions from the page. Data never leaves the laptop.

Every page also gets three animated diagrams for free (web/run-viz.js): a pulse card (progress ring, verdict-mix bar, working/elapsed), the court map (claims → lens agents → ruling → decision; particles flow into working agents, nodes pop into their verdict colour) and a timeline (one growing bar per agent + markers for rulings, questions, contests). They key off agent labels <lens>:<subject>, claim events (subject = the same id) and ruling/decision events — emit those and the diagrams draw themselves.

You are the only writer of semantic events. Workflow scripts cannot write files, so the page reads per-agent progress passively from the Workflow's transcript dir once you bind it — you never emit per-agent events yourself.

Protocol

1 · Start (before the first fan-out)

curl -sf localhost:8765/api/runs >/dev/null || echo "need server"

• need server + port free → start mindgap serve --no-open in the background (Bash run_in_background). Port 8765 held by a server WITHOUT /api/runs = an old process → don't kill it; serve on --port 8777 and use that port in the URL.
• mindgap run start --skill <skill> --title "<what is being decided>" [--port N] → prints the run id + URL. Give the user the URL in your next message. With MINDGAP_BROWSER=iterm it also opens the page in an iTerm2 split pane beside this session — still give the URL.
• Arm the back-channel: Bash with run_in_background: true running mindgap run inbox <run-id> --once. It blocks silently until the page posts, prints that burst (one JSON message per line) and exits — you are notified exactly then, never on a timer. Reply to EVERY line, then re-arm the same command at once. It resumes from a saved cursor, so anything posted while it was down arrives on re-arm, each message exactly once. Do NOT use a Monitor for this: a Monitor expires every ≤30 min and each expiry wakes you for nothing (a real loop session logged 29 empty expiries).