Dashboard (eq dashboard)¶

Launches the FastHTML dashboard, the only UI for browsing saved runs. The Streamlit viewers it replaced, eq redteam ui and eq sim ui, have been removed.

When the server starts, it opens the dashboard in your browser unless you pass --no-browser. The command reads .env in the current directory; existing shell variables take precedence.

For what the dashboard shows once it is open — the run index, the red-team and simulation walkthroughs, and applying recommendations to an agent — see Dashboard. This page covers the command only.

eq dashboard [PATHS]... [OPTIONS]

What gets scanned¶

The argument is what decides which runs appear, and the three forms behave differently:

• No path — scans both default stores together: .evaluatorq/runs/ (red team) and .evaluatorq/sim-runs/ (simulation). This is the usual invocation.
• One or more directories — scans exactly those, together. Useful for putting simulation runs from one repo next to red-team runs from another.
• A file — scans that file's parent directory, so sibling reports still resolve, and prints the direct URL for that one report. You land on the report rather than the index.

# every saved run, both stores
eq dashboard

# simulation runs only
eq dashboard .evaluatorq/sim-runs

# two stores from different checkouts, side by side
eq dashboard ~/work/api-agent/.evaluatorq/runs ~/work/support-bot/.evaluatorq/sim-runs

# open one report directly
eq dashboard .evaluatorq/runs/red-team-2026-08-18T09-14-02.json

# start the server without opening a browser
eq dashboard --no-browser

Binding¶

--host defaults to 127.0.0.1, so the dashboard is reachable only from the machine running it. Binding elsewhere exposes every saved run — transcripts, system prompts, and judge verdicts — to anyone who can reach the port. There is no authentication layer. Put it behind one before binding to 0.0.0.0.