nv: the same agents, the same memory, the same permission checks Chat uses, run headless. Part of Personal, not a separate purchase.
A scheduled task at 3am. A Windows box you only ever reach over a remote session or SSH. A CI runner that starts, does the job, and shuts down. None of those have anyone sitting in front of them, so an app with a window is not a lighter option there, it is not an option at all. The CLI is not a stripped-down way to use NeuralVault for that machine, it is the only one that fits how it actually runs.
If your own workflow already lives in a terminal, the same is true for you: buy NeuralVault Personal, install it, and never open the app it comes with at all. There is no separate CLI product to choose instead. One licence, one binary, same fleet and memory either way — you are just picking the door you walk through.
run, not one.nv run <prompt> reaches the identical engine a typed message in Chat does. The other twelve, transcribed from nv --help, reach everything else.
nv boardThe pipeline board: create, move and delete cards. Same AgentFleet gate as the app, same file.
nv orchestraPut several models on one problem and compare what comes back, cost estimated before it runs.
nv searchNotes matching your words, best first, the same hybrid lexical and vector search the app uses.
nv notesBrowse the vault: folders, ls, read. A direct call, not a model deciding whether to look.
nv sessionsList, read, find, archive, unarchive and rename past conversations from a terminal.
nv auditThe vault’s audit log, newest first: what ran, when, and why it decided to.
nv connectorsConfigured MCP connectors, read-only: what is wired up before you script against it.
nv projectsThe Projects shelf, read-only, so a script can see what you are already tracking.
nv pluginsList grants and revoke one by id, the same registry the app’s plugin host reads.
nv modelsList, browse the catalogue, or set which model a role uses, without opening Settings.
nv keysCheck, set or clear a provider’s API key in your OS credential store.
nv settingsRead local settings: provider defaults, agent-tier overrides, custom endpoints.
Every tool is denied by default: a headless run has nobody to ask, so anything the model tries that you did not explicitly allow is refused and it carries on knowing that. --allow-tool and --allow-all-tools name what a run may touch, once, in the command that starts it. Exit codes are three states, not two: 0 is a clean answer, 1 is an error, and 2 means the model wanted to do something you had not allowed, which a script can branch on instead of grepping the output for it. --json turns the whole run into one event per line for anything reading it.
A one-line install (irm ... | iex, no download page, no zip to extract) is a familiar shape for anyone who has installed a developer CLI before, and it is the one worth matching. Ours is built and works, and the install command above is real, but nothing is live for it to fetch yet: nv isn’t in any released download today, standalone or inside the app installer.
Gated to Personal at the binary level, not just per command. In developmentBuilt and tested, gated to Personal. Not yet merged to the app’s integration branch, and not in any released installer.
Want the board, the dashboard, chat, and everything else too?