Skip to main content
pome inspect reads a run’s artifacts and prints a human-readable summary: trace health, recorded events, and per-criterion score verdicts. Use it after pome run to debug failures without opening the dashboard.

​
Usage

pome inspect <run> [options]

​
Arguments

ArgumentRequiredDescription
<run>YesRun id, path to a run directory, or latest (most recent run under --artifacts-dir).

​
Options

FlagDefaultDescription
--artifacts-dir <dir>runsBase directory where pome run writes artifacts.

​
Output

Prints:
  • Run id and artifact directory path
  • Trace health summary (event counts, gaps, proxy capture status)
  • Rendered event timeline from events.jsonl
  • Aggregate score and per-criterion pass/fail/skip lines from score.json

​
Examples

# Most recent run
pome inspect latest

# Specific run directory
pome inspect runs/01-bug-happy-path/ses_abc123

# Custom artifacts location
pome inspect latest --artifacts-dir eval/results

​
Exit codes

CodeMeaning
0Report printed successfully.
2Legacy events.jsonl format detected (pre–FDRS-403 schema). Re-run with a current CLI build.
Generate a fix prompt for a failed run: 
pome fix-prompt runs/<scenario>/<run-id>/events.jsonl \
  runs/<scenario>/<run-id>/score.json \
  scenarios/<scenario>.md