Results Viewer

This directory contains a Streamlit app for exploring saved realtime eval runs from the crawl, walk, and run harnesses, plus bootstrap-generated eval folders created under examples/evals/realtime_evals/.

The app auto-discovers run directories under:

• crawl_harness/results/
• walk_harness/results/
• run_harness/results/
• *_realtime_eval/results/ when the folder includes bootstrap_manifest.json

What It Shows

• Comparison View: compare summary metrics across one or more saved runs
• Run Viewer: inspect a single saved run, including:
  • results.csv rows
  • crawl/walk input and output audio artifacts
  • crawl/walk per-example event logs
  • run-harness simulation transcripts, event logs, and turn audio

Note: run_harness runs are inspected via the app's Simulation Viewer, which has a different UI and a different artifact set than the crawl/walk viewer.

Run Locally

From examples/evals/realtime_evals/:

uv venv .venv
source .venv/bin/activate
uv sync --group dev
cd results_viewer
uv run streamlit run app.py

Then open the local URL that Streamlit prints, usually http://localhost:8501.

If you are using the pip-based install path instead of uv, install the dev dependencies first so streamlit is available:

pip install -r requirements.txt -r requirements-dev.txt
cd results_viewer
streamlit run app.py

Expected Data Layout

The viewer expects each saved run directory to contain:

• summary.json for aggregate metrics
• results.csv for per-example results

For crawl and walk runs, the app can also display:

• audio/<example_id>/input.wav
• audio/<example_id>/output.wav
• events/<example_id>.jsonl

The app discovers runs recursively, so nested result directories are fine as long as those files are present.