Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pome.sh/llms.txt

Use this file to discover all available pages before exploring further.

dashboard.pome.sh is the web view for everything you run with pome — registered agents, the clones they hit, the runs themselves, and the LLM-judge handoff for each one. pome run records to the dashboard by default. Local copies of the artifacts (tool_calls.jsonl, score.json, state snapshots) also land on disk under runs/<scenario>/<run-id>/.

​
What you’ll find

​
Agents

Each agent you’ve registered (via /pome-setup or pome register agent) shows up here. The agent page lists:
  • The clones this agent has been tested against.
  • Every run associated with it, newest first.

​
Runs

A run is a single scenario execution. The run page shows:
  • The full trace — every tool call the agent made, in order.
  • The score against the scenario’s expected end state.
  • An LLM-judge handoff — a concise summary plus an actionable suggestion to fix or improve the agent. Use it as the next prompt back to your coding agent.

​
Clones

A clone is a stateful instance of a twin (GitHub clone, Stripe clone, …) used by a run. From a clone you can see which agents have run against it and inspect the state diffs run-to-run.

​
How runs end up here

Anything that talks to the backend lands on the dashboard:
  • pome run <scenario> from the CLI.
  • /pome-test invocations.
  • Any agent you’ve registered with pome register agent once it makes scored runs.
The CLI uses the API key from ~/.pome/credentials.json (written by pome login) or POME_API_KEY (CI). See Getting started for the login flow.

​
Open it

open https://dashboard.pome.sh
Or grab a direct link from the URL /pome-setup prints after registering your agent.

​
Next

Skills

/pome-setup registers the agent and gives you the dashboard URL. /pome-test populates the runs.

CLI reference

pome run, pome register agent, and the auth env vars.