Metrics

What the console spent, what it is driving, and how far along it is — in Prometheus text.

curl -s 127.0.0.1:4620/api/metrics | head -20

Everything the cost and progress pages show is on this endpoint too, so a figure can be alerted on rather than watched. It is a plain read like every other GET: no flag turns it on, no token guards it, and the console binds to loopback.

20 families. The list below comes from viewer/server/analysis/metrics.ts METRIC_FAMILIES, and viewer/test/docs-parity.test.ts holds this document to it — a family added to one and not the other fails the suite, as does calling a counter a gauge.

Scraping it

# prometheus.yml
scrape_configs:
  - job_name: phase-console
    static_configs:
      - targets: ['127.0.0.1:4620']
    metrics_path: /api/metrics

The port is whichever this console is on — phase-console list prints it. Two consoles on one machine are two targets; phase_console_build_info carries the instance name to tell them apart.

Raise scrape_timeout above your first scrape. The endpoint reads every plan's board, so the first request after a console restart pays the cold read for all of them and everything after it is served from cache — measured on a 119-plan library: 20 s cold, 10–13 ms warm. That is the same cost the Plans page pays, not something this endpoint adds, but Prometheus's 10 s default will time the first one out and retry. phase_console_scrape_duration_seconds reports it, so you can see which kind of scrape you got.

The families

Labels. slug on everything per-plan; state on phase_console_phases (done · ready · in-progress · waiting · stuck); status and closed on phase_console_plans; slug and status on phase_console_runs; rung and outcome on phase_console_ladder_rungs_total; version and instance on phase_console_build_info.

Never a run id — a run id is minted per boarding, so labelling by one would mint a dead series every time the autopilot starts a run, and a scraper keeps those forever. Per-plan is the granularity the questions are asked at.

Three things to know before you alert on these

The names are a contract. Once you scrape this, a rename breaks your dashboard silently, weeks later. So a family is never renamed or repurposed and a label is never added to an existing family — new facts arrive as new families. _total is a counter and everything else is a gauge, with no exceptions: rate() over a mislabelled family is wrong in a way nothing reports.

The money adds up in one direction only. Every session books the same dollars to its run total and to its phase record, and again to the ladder rung that caused it when one did. So:

• phase_console_spend_usd_total is the money. It is the one to sum.
• phase_console_phase_spend_usd_total is the same money, seen per phase — equal in a healthy run.
• phase_console_ladder_spend_usd_total is a subset of both. Adding it double-counts repair.
• phase_console_spend_residual_usd should be 0. A non-zero value is a run file disagreeing with itself, which is worth an alert of its own.

The three worktree families are ABSENT, not zero, until a run isolates. phase_console_worktrees, phase_console_worktree_disk_bytes and phase_console_branch_conflicted_files report only on runs working in a checkout of their own (Give this run its own checkout, on the launch form — see what you control), so on a console that has never isolated anything the families do not appear at all — absent() is the alert to write, not == 0. Once a run does isolate, phase_console_branch_conflicted_files is 0 while its branch is clean, which is a different fact and the one worth alerting on: a non-zero value means a merge conflict is already sitting between two live branches, and the console raises the same fact as a conflict inbox item with a one-press remedy. phase_console_worktree_disk_bytes goes absent for one slug where du could not answer, without taking the other slugs' samples with it.

A counter resets if you delete a run file. That is the only way these go backwards, and rate()/increase() already handle it. Nothing here is reset by restarting the console: the numbers are read from the run files on disk, not from process memory.

What is NOT here

No note, no title, no path, no owner, no session id, no prompt — a scrape is counts, slugs and money. That is what makes it safe to leave open on a laptop, and it is deliberate rather than incidental: if you need the words, the pages have them.

Nothing about cost per model either. It exists per plan (Insights ▸ What this plan cost ▸ By model, and the CSV) but a phase books to the model it ended on, so a fallback mid-run makes the per-model split a summary rather than an accounting — not a number to alert on.