NOVA-CLI 1.0
CURRENTYour AI developer, ready for real work
NOVA-CLI 1.0 is our biggest release yet. Choose the AI model NOVA works with. Show it a screenshot, a PDF or a recording. Get an honest result on every task, backed by your project's own checks. Close your terminal and pick up the same task days later. And when you'd rather not live in the terminal, open NOVA App in your browser. NOVA-CLI 1.0 is included on every plan, including Free.
- # Legacy unverified execution
- protected_paths: []
- approval_required_for: []+ version: 1
+ protected_paths:
+ - .github/workflows/**
+ - migrations/**
+ approval_required_for:
+ - git push
+ - dependency installRelease Engineering Highlights
Type \model and pick from the models on your plan with the arrow keys, a number or \model search. NOVA remembers your choice for each project, and every part of a task uses it: planning, fixes, commit messages, memory, documents and data work. Models your plan doesn't include are shown as locked, with the plan that unlocks them. From your terminal, nova models lists and searches them.
Attach an image, PDF, video or audio file with @, or drag it into the terminal. On Windows, you can also paste a file you copied in File Explorer. Type @ on its own to browse the current folder. Share a screenshot and NOVA can tell whether you want a design copied or a bug fixed. Audio and video work with models that support them.
A visual workspace for NOVA that opens in your browser and runs entirely on your computer. Start it with nova-app or \nova-app to chat with NOVA, browse your sessions and skills, see your Git status, set up scheduled work and explore how your project fits together.
NOVA builds a private map of how your project connects and uses it automatically for architecture and impact questions. Ask the map yourself with \trace (where something is defined, called and used) and \impact (what a change could affect), and manage it with nova intelligence. The map is built and kept on your computer, and your code is read, never run, to build it.
Run nova init to give your project rules that apply to every change: paths that need a person's approval, protected branches, checks that must pass and packages that may be installed. Four instant reports, nova brief, nova verify, nova risk and nova handoff, need no sign-in and no AI, so they fit straight into CI.
A task that changes files now ends with one result (PASS, FAIL, BLOCKED, SKIPPED or UNVERIFIED) and NOVA's record of what changed, what was checked and what failed. NOVA never reports a pass when no check ran, and saves a readable handoff note in your project.
Close NOVA and continue the same task days later with nova resume. NOVA restores the goal, plan and decisions, checks what changed while you were away, and shows any result that no longer holds as stale. Use nova sessions to list, show, rename, complete, abandon or delete your sessions.
\debug, \testing, \review, \refactor, \explain and \security bring focused know-how to everyday engineering jobs. NOVA picks the right one for you, or you can name one yourself, including in scripts with --skill.
Create a skill with nova skills create, add a skill folder you already have with nova skills add, and remove one with nova skills remove. Project skills live in your repository, so your whole team gets them.
Ask NOVA to clone a Git repository and set it up. It asks once, for that repository only, then carries on working inside it.
nova setup-git installs Git for you on Windows and macOS, and shows you the right command on Linux.
nova uninstall lists what it will remove and asks first. Your settings, memory, sessions and skills stay unless you add --purge, and your projects are never touched.
Deleting files, installing software, committing, pushing, rewriting Git history, deploying and opening files that hold secrets now always ask, in every permission mode, including auto. Saying no to NOVA's plan now stops the whole task, not just its first step.
NOVA keeps track of what it changed and commits only that, leaving your unfinished work exactly as it was. If you and NOVA both changed the same file, NOVA tells you instead of deciding for you.
When a request could mean two different jobs, NOVA asks which one you meant before it starts.
If a model stops responding in the middle of a task, NOVA switches to another so the work still finishes, then tells you it switched.
NOVA settles the colours, fonts and spacing before it writes the first page, and a screenshot you share now guides the whole design.
\remember tells you where each note landed. \memory shows where every entry came from, including which ones NOVA decided on its own, and whether each is used on every request.
Passwords, keys, tokens, cookies and signed links are masked in the sessions, logs and handoff notes NOVA saves, and NOVA can still edit the lines that contain them.
When NOVA reports problems outside the part of the project you asked about, type \fix and it fixes those too, then checks again.
NOVA won't overwrite a file that changed after it last read it, so a change you made in the meantime is never lost.
NOVA follows your project's own settings for what to check, picks the right test command when a project has more than one, and keeps the exact test command you asked for.
nova -p gains --allow-delete and --skill. --timeout now stops a run even in the middle of a command, and a run that hits a limit never exits as a success.
Quick questions and long sessions send far less with each request, so they use fewer credits.
Approvals, progress, results and attachments share one consistent look. Installing Git, Node.js or Repository Intelligence shows a progress indicator and one plain line instead of the installer's own output, and a long changed line now lines up under its code when it wraps.
nova --version, the launch screen and nova doctor show which build of NOVA you're running, which makes reporting an issue easier.
nova usage and nova logout now work straight from your terminal.
NOVA stores your sign-in in Windows Credential Manager. If it can't store it securely, it saves nothing and tells you.
Choosing a model your plan doesn't include now says so, instead of asking you to log in again. An attachment that's too large no longer suggests upgrading your plan.
A check NOVA planned but never ran no longer counts as passed, and a site NOVA couldn't check is reported as not verified.
A check that was cancelled is no longer reported as a failure in your project.
Replying in the middle of a website build, including typing continue, keeps the kind of site NOVA was building and what you agreed.
Settings saved in your settings files now take effect, and settings NOVA no longer uses are ignored quietly instead of being reported as typos.
On Windows, NOVA creates folders itself instead of reporting that mkdir is missing, handles files with Windows line endings (including skills written in Notepad), and no longer interrupts the whole terminal while checking for another running copy.
Starting a project that's already running reuses it, instead of opening a second copy on a new port.
When an MCP server fails to start, NOVA shows the server's own reason.
Approval prompts show the actual command NOVA wants to run.