Skip to main content

​
Synopsis

​
Description

pome eval uploads a run directory you already captured and prints the score the cloud returns. It is the second half of the capture-and-evaluate split. pome run --local captures a trace without grading it; pome eval is how that trace gets a verdict. There is no local scoring — the CLI captures, the cloud grades.

​
Arguments

<artifacts-dir> is runs, unless the global --artifacts-dir points somewhere else — that directory’s latest.json is what picks the run.

​
Options

Plus the global flags — --api-url, --artifacts-dir, and -V, --version.

​
Requirements

pome eval needs a control plane serving POST /v1/eval-sessions, and credentials — pome login or POME_API_KEY.

​
Examples

​
Exit status

See the canonical table. A run whose criteria could not all be graded is INCOMPLETE and exits 1, the same as a run that scored below its threshold — read the printed verdict word to tell them apart.

​
See also

  • pome run — --local captures the trace this command grades.
  • pome inspect — read a scored run in the terminal.