It's Waiting For You

A local, read-only dashboard for every Amplifier recipe

The Amplifier Recipe Dashboard

Launch an Amplifier recipe, and you go blind

Recipes are long, multi-step jobs. Once one is running, you can't easily tell if it's progressing, stuck, or quietly waiting on you. The recipe dashboard is the one command that shows every session at a glance.

First, is it real? →

Proof

It's real, and it's running

A working web dashboard for monitoring Amplifier recipe executions — built by a single author between 2026-04-03 and 2026-05-05.

So where does its data come from? →

~6,689

lines across package, frontend, templates & tests

35

passing tests (pytest)

7

commits on main, sole author Samuel Lee

1

command to open it (uvx one-shot)

The Data Already Exists

Every recipe run already checkpoints itself

The recipe engine (amplifier-bundle-recipes session.py) writes a state.json on each step — recording completed steps and any pending approval stage — at the exact path the dashboard reads.

But that file is buried on disk. →

Writesstate.json under <slug>/recipe-sessions/…
Recordscompleted_steps for each finished step
Flagspending_approval_stage when it needs you

The Blindness

The state exists — but it's buried on disk

A launched recipe leaves you scrolling terminal logs to guess whether a run is still running, has stalled, or is stuck on an approval. The checkpoint data is right there, and you still can't see it.

So the dashboard reads those same files. →

How It Works · Read-Only

It reads those same files, and never writes yours

The dashboard reads state.json read-only (read_text / json.loads / yaml.safe_load). No LLM, no API keys, no provider — the only outbound call is an optional version/upgrade check.

From those files, it builds status. →

Reads only — never writes into your session dirs
No LLM, no API key, no provider needed
Binds to localhost (127.0.0.1) by default
Only network call: optional self-upgrade check

How It Works · Classification

Raw files become 7 trustworthy states

It classifies every session into running, waiting, idle, done, stalled, cancelled, or failed. Multi-signal freshness — max(state mtime, agent activity) — keeps a busy run from looking idle (added in PR #5).

And one of those states is for you. →

running

waiting

idle

done

stalled

cancelled

failed

The Payoff

"Waiting for you" is now impossible to miss

A pending approval maps to a first-class waiting status. It's a filter tab in the discovery view and an approval banner in the detail view — the stuck recipe surfaces itself.

And all of it comes from local files. →

The Takeaway

One command. Local. Nothing leaves your machine.

One command opens the dashboard and auto-opens your browser on 127.0.0.1:8181 — read-only visibility into every recipe, with nothing about your recipes leaving the machine.

See what your recipes are doing.

# one-shot, auto-opens the browser on 127.0.0.1:8181
uvx --from git+https://github.com/samueljklee/amplifier-recipe-dashboard \
  amplifier-recipe-dashboard

Sources

Research Methodology

Feature status: Active

Repository: samueljklee/amplifier-recipe-dashboard (verified via a fresh clone of the default branch; producer contract checked against local amplifier-bundle-recipes).

Data as of: latest commit d61c0d5, 2026-05-05.

Commands run:

gh repo view samueljklee/amplifier-recipe-dashboard
gh pr list --repo samueljklee/amplifier-recipe-dashboard --state all --json number,title,mergedAt
git log --reverse --format='%h %ai %s' — first commit c714bb1 (2026-04-03); latest d61c0d5 (2026-05-05)
git shortlog -sne --all ; git log --oneline | wc -l — 7 commits on main, sole author
wc -l amplifier_recipe_dashboard/*.py static/* templates/* tests/*.py — 6,689 total lines
grep -rn 'read_text|json.load|yaml.safe_load|.write|json.dump' — reads only; no writes into session dirs
grep -rn 'urllib|openai|anthropic|api_key|litellm' — no LLM/keys; only optional upgrade check (cli.py urllib)
uv run ... pytest -q — 35 passed, 1 warning

Gaps: README "Tech Stack" prose (Flask/Waitress/Click) is stale after the FastAPI migration (PR #4); current stack is FastAPI + uvicorn + argparse. PyPI availability of the upgrade package and live session paths were inspected in code, not exercised against live data.

Primary contributor: Samuel Lee — sole author, 7 commits on main (all PRs #2–#7).