Skip to main content
The pome CLI runs agent tasks against deterministic twins, records every tool call, and scores the results. Hosted runs record and score on app.pome.sh by default; pome run --local runs the in-process twin and records the trace without scoring (evaluation is a hosted feature).

Command index

Other commands

The CLI no longer installs agent skills. The coach skills are installed by the skills CLI and talk to Pome over MCP:
That is what pome install prints. See the Quickstart for the full walkthrough.

Auth resolution order

  1. POME_API_KEY environment variable.
  2. macOS Keychain entry (security find-generic-password -s pome-sh) on macOS.
  3. ~/.pome/credentials.json written by pome login.
If none are set, hosted commands fail fast. Use pome run --local to bypass auth and run against a local in-process twin (trace only, no scoring).

Exit codes

Stage 1 known regressions: some pome run paths return exit code 2 or 3 when 1 was documented. CI consumers branching on $? should not yet treat this table as a hard contract. See troubleshooting.
A --local run is not scored, so its exit code reflects only whether the agent ran cleanly (0) or errored/timed out (3) — exit 0 from --local means “trace captured,” not “task passed.” Do not gate CI on a --local exit code.