NeuralVault 2.0 is releasing very soon. It is not out yet, there is no download today, and this post is not a release announcement. It is an update on where things stand, and on what has changed since the post that announced it, which still describes the release and is not repeated here.
Where things stand
The build is in its last stretch. We are not giving a date, because the changelog is where a release date becomes a fact, and an earlier target for this release has already passed without it going out. The moment a version is public, the changelog and the 2.0 page will say so, and the Free download comes back with it.
Until then nothing described on this site as part of 2.0 can be downloaded, and the Free edition is not on general download.
What has been tightened since the last post
Most of the last stretch has gone into things you only notice when they are wrong.
Usage data starts off. The first-run switch for anonymous usage data now starts off, and stays off until you turn it on. Pressing Continue or Skip for now records off.
Code mode is harder to trick. A repository can no longer make the shell tool run a program named in its own git config. A repository whose instruction file reads like injected orders now makes every change ask first, instead of riding on a remembered answer.
Screen readers hear what changes. Search results, toasts and the audit-log filters are announced as they change, rather than only drawn on screen.
Bringing your history across. Importing from Claude Code or Codex now takes the most recently written conversations, not an arbitrary set.
What this means for Personal
Personal is planned as monthly plans that include a usage balance for NeuralVault routing, alongside a software-only licence for people who bring their own keys. None of it is on sale yet. The Personal page carries the details and says so plainly, and it will not turn into a buy button until the release is out.
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.