Newton CLI Command Playbook
Use this skill whenever you need to operate Newton from the command line and want a reminder of what each subcommand expects.
Quick Start
- •Run
newton --helpto see the global description and available commands. - •Inspect any subcommand with
newton <command> --helpto view supported options. - •Refer to the reference sheets in this skill for typical workflows, mandatory arguments, and example invocations.
- •Adjust values (paths, IDs, formats) to match your workspace before executing commands.
Primary Workflow
- •
newton run WORKSPACE: launch full optimization loop. See references/run.md. - •
newton step WORKSPACE: manually advance one iteration. See references/step.md. - •
newton batch PROJECT_ID: consume queued plans for a project with before/after hooks. See references/batch.md. - •
newton status EXECUTION: inspect state. See references/status.md. - •
newton report EXECUTION: summarize results. See references/report.md. - •
newton error EXECUTION: diagnose failures. See references/error.md.
Each reference file lists required arguments, optional flags, and example invocations so you can run Newton without diving into implementation details.
Usage Notes
- •For additional context, check
newton --helpor the specific command's--helpoutput at any time. - •Strict mode toggles (
--evaluator-cmd, etc.) require valid executable commands available in your environment. - •When specifying workspaces or artifact paths, provide absolute or workspace-relative paths that already exist.
- •Always make sure you have write permissions to the workspace before running
runorstep.
Helpful Commands
bash
cargo run -- --help cargo run -- run ./workspace --max-iterations 2 --max-time 60 cargo run -- status exec_123 --workspace ./workspace