NeuralVault 2.0 is not out yet, and there is no download today. This is a plain tour of what you will notice when it is, written for someone deciding whether to wait for it. The full list, entry by entry, is on the roadmap, and the exact changes land in the changelog when a version ships.
What you will notice first
A rebuilt app. The interface has been rebuilt around the two things people do all day: talking to Cortex and working in your vault. Settings, the dashboard and the library are rebuilt around that. The engine that stores your work carries over unchanged, so what is new is everything you look at, and nothing that holds your notes.
One account. You sign in once, across the website and the app. There is no licence file to install and no key to paste, and your access follows your plan while the app is running.
Agents that ask before they act
Writes you approve. Cortex can create, append to and move notes, and add a card, a task or a log line. Each change waits on a card that shows exactly which files it touches, and one control puts them back afterwards.
A guard on what agents can do. Before an agent runs a command, writes a file or sends something out, a check looks at what it is about to do. It refuses or asks when the action would leak a key or password, install unknown or look-alike software, run a download piped straight into a shell, write code with a known flaw, or carry out an instruction hidden in something it read.
We test the guard against scenarios held back from its rules, and we track every one it misses. On the first held-out set it caught 131 of 143 attacks, and on the larger and harder sets it scores lower. The scoreboard on the 2.0 page shows all of them with their dates, because one number depends on which test you pick.
A memory you can tell things to. Say "remember that" and the fact is kept and read back into later conversations. Say "from now on" and the rule goes into your own instructions file, which Settings shows you.
Choosing who serves a turn
Routing in the model picker. NeuralVault routing sits beside your own keys, so who serves a turn is a choice you make per model, not a mode for the whole app. You can set how hard a model thinks and attach images where a model supports them.
Usage you can see. A balance, and a running ledger of what each turn cost. Or keep using your own key, and nothing is metered. Both stay available, and none of the plans is on sale yet.
Yours to keep
Workspaces and folders. Group chats into named workspaces, nest folders inside them, and act on several at once. Deleting a workspace never deletes a chat.
Export. Copy your notes to a plain folder you choose. Nothing is converted, and nothing in your vault changes.
A choice about usage data
During setup you are asked whether to send anonymous usage data, and you can change your answer at any time in Settings, under Privacy.
For developers
The nv command line, for scripts, CI and cron, is coming soon. It is built and tested, and it is not in a public download yet. See the command line.
What is not in 2.0
Sync across your own devices, an approvals queue for work that runs while you are away, and macOS and Linux builds are not part of 2.0. The Business edition follows it and has no date yet.
How to hear when it lands
The release list on the services page sends one email when a version goes out, and the box at the bottom of the blog sends one email per post. Either is enough.