Skip to main content
The pome CLI runs agent scenarios against deterministic twins, records tool calls, and scores results. Hosted runs record to app.pome.sh by default; set POME_LOCAL=1 for engineer-only in-process local twins.

Command index

CommandWhat it doesReference
pome runRun one or more scenario files against a twin and score the agent.run
pome sessionCreate, list, and stop hosted sandbox sessions.session
pome scenariosBrowse and copy the bundled scenario library.scenarios
pome compile-seedsCompile prose seed sections into .seed.json sidecars.compile-seeds
pome inspectPrint a human-readable report for a run.inspect
pome initScaffold scenarios/, examples/agents/, and pome.config.json.init

Other commands

CommandWhat it does
pome login / pome logoutSign in via browser and store a team API key; clear local credentials.
pome register agent <name>Create a cloud agent and write agentId + agentSlug to pome.config.json.
pome docs [topic]Read bundled docs in the terminal or print docs.pome.sh URLs.
pome skills installInstall /pome-setup and /pome-test into ~/.claude/skills/.
pome twin start <name>Start a standalone GitHub twin on a local port.
pome twin reset / pome twin statusReset or inspect standalone twin state.
pome fix-promptGenerate a paste-into-IDE fix prompt for a failed run (BYOK LLM).
pome healthIn-process smoke check against the bundled GitHub twin.
pome versionPrint the CLI version.

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_LOCAL=1 to bypass auth for local in-process runs.

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.
CodeMeaning
0All scenarios passed.
1At least one scenario scored below threshold.
2Twin or runner error (network, 5xx, twin spawn failed).
3Auth error (401/403). Re-run pome login.
4Quota exceeded.
5Usage error (bad flags, missing files).