monte CLI is the only write path into the platform. This page states the conventions once, then lists every command.
Conventions
- Default subverb.
monte eval mathmeansmonte eval run math. Same fortrain. Theenvgroup has no default on purpose: list and install are different intents. - Confirm before launch.
eval runandtrain runprint the Run plan, then asklaunch?. Skip the prompt with--yes. Without a TTY the prompt refuses (E_CONFIRM) instead of hanging.--dry-runprints the plan and launches nothing. The plan you approve is the exact object persisted asplan.jsonand hashed into the row’s provenance. - Typed confirm for promote.
promotedoes not ask y/n. You must pass--confirm <measurement-name>, typed out. A mismatch is the sameE_CONFIRM. --json. Supported oneval run,train run,status,show,env list, andconfigonly. Stdout carries pure JSON: the human plan summary moves to stderr. One trap:status --jsonomits the checkpoint ladder that the human view prints.- Refusals. Anything the platform declines exits 3 or higher with
CODE: cause (fix)on stderr. The fix is part of the message.
Commands
monte init
measurement.json. Refuses an existing name (E_MEASUREMENT_EXISTS).
monte eval
monte train
E_NO_BASELINE). --smoke runs a capped micro-chunk that is never evidence. --chained only matters with --smoke: real runs always chain.
monte status
monte logs, show, stop
logs prints the Run’s event file as JSON lines. show prints one full row with all provenance fields. stop terminates a running Run and the row reads as abandoned.
monte promote
--dest, sha256-verified. It then prints the file count and the destination disk usage.
monte env
list shows each Environment and its Gym benchmarks. install verifies frozen data against its manifest and registers the benchmark configs. Install is idempotent. A mock-only Environment prints a note instead.

