Back
Reference // Options & Exit Codes
Options & Exit Codes
Docs › Reference › Options & Exit Codes
Options & Exit Codes
Options for running NOVA in one shot with nova -p, and what its exit codes mean.
Options
| Option | What it does |
|---|---|
| -p "task", --print | The task to run. Or pipe it in: echo "task" | nova -p |
| --permission-mode <mode> | plan, ask, acceptEdits, overdrive or auto. |
| --allow-delete | Allow deleting files in this run, and nothing else. |
| --output-format <format> | text (default), json or stream-json. |
| --max-turns <n> | The most steps NOVA may take. |
| --timeout <seconds> | Stop after this long. |
| --skill <name> | Use a specific skill. Repeat for more than one. |
| --continue, -c | Continue the most recent session. |
| --resume <session> | Continue a specific session. |
| --cwd <folder> | Run in another folder. |
| --stdin | Wait for all piped input before starting. |
| --no-mcp | Don't connect to MCP servers for this run. |
Exit codes for nova -p
| Code | Meaning |
|---|---|
| 0 | Finished |
| 1 | Task unfinished, not verified, or the step limit was reached |
| 2 | Invalid command line |
| 3 | Not signed in |
| 4 | Out of credits |
| 5 | --timeout reached |
| 6 | Refused for lack of permission, with no other result |
| 130 | Interrupted |
Note:Exit code 0 doesn't always mean files changed. If an edit was refused and NOVA explained why, the run still exits 0. Check the Changed line in NOVA's record.
Exit codes for reports
For nova brief, verify, risk and handoff:
| Code | Meaning |
|---|---|
| 0 | Everything required passed |
| 1 | A required check failed or never ran |
| 2 | Blocked: a person needs to approve |
| 3 | Not a project NOVA can check |
Join our Discord
Chat with our engineers and become part of the active NOVA developer community.
Need help?
Open an issue on GitHub or email support@bridgeye.com.