v3.3.4October 13, 2026
Orientations for tasks, and updates that reach every project.
Two reports shaped this release. In the first, an agent was told something in a sentence, with no task in it, and vexp answered with code. From eight words up the per-prompt hook oriented every prompt, so a remark to the agent received functions whose names were two of its verbs, spent one of the session’s three orientations, and the tasks that followed got none. On 599 real prompts, read and labelled one by one, 192 of the 259 conversational ones had received code. 3.3.4 puts a typed prompt through a gate: it is oriented on evidence, or it gets nothing and nothing is charged. On the same prompts 37 receive code, and replayed in their real sessions the tasks oriented go from 67 to 83, and the tasks left with nothing by the session’s limit from 134 to 61. On a large Go repository the orientation itself now arrives in time: 39 of 45 inside the hook’s three seconds, where 24 did. The second report came from a user who updated the VS Code extension and listed what an update leaves behind: a config entry still pointing into the previous extension folder, a Node path the next brew upgrade would remove, daemons still running the previous version, and no command that showed them all or stopped them all. 3.3.4 goes through each of those.
A sentence to the agent is searched, and left alone. A typed prompt of one paragraph now goes through a gate before it is oriented. A file you name, or a symbol typed as an identifier, is evidence, and the prompt is oriented as before. An exact match on an ordinary word that no second word of the prompt agrees with is not read as naming that symbol, and a name the index itself wrote into the query is never shown as something you typed. With nothing to stand on nothing is sent, no orientation is spent, and the ledger records the step that stopped it. To name a symbol whose name is also an ordinary word, write it in backticks, as a call, or with its file. The one-line notice for a prompt that matched nothing is sent once per session and never charged. Of 61 task prompts whose orientation held a file the agent then used, 54 keep one, and the share of served pivots that were used goes from 25.7% to 41.9%.
What the gate left alone is counted, everywhere. A prompt that is searched and left unoriented moves none of the ledger’s numbers, so a week of sentences to the agent would have read as a week in which no hook ran, and vexp doctor would have concluded that no agent was using vexp. vexp savings, the usage report, vexp doctor, the sidebar’s Activity section and the index_status tool count three things by name: prompts searched and not oriented, notices withheld because the session had already had one, and definition lists served alone while the seed was switched off. A week made of them is an OK line in doctor: the prompt hook is reaching vexp.
On a large repository the orientation arrives in time. To build an orientation the hook asked for a whole context capsule, and the capsule went on to look for the neighbourhood of every pivot, the files that change with it and its dependents. The orientation prints the pivots and reads none of that. On a Go repository of about 17,000 symbols and 720,000 edges that search took about 85% of the hook’s time. The hook now asks for the pivots alone, which are chosen before any of it and are the same ones in the same order. Measured on 45 checkouts of that repository: orientations delivered inside the three seconds 39 against 24, late 3 against 18, median 0.6 s against 2.2 s. On 298 prompts over 60 smaller repositories the output is identical, and run_pipeline and get_context_capsule are unchanged. A prompt asked again in the same words gets the orientation it got the first time.
A name typed as code is read wherever it stands. The classifier of a typed prompt read its first twelve candidate words and stopped. A long prompt that opened on a paragraph of ordinary words was classed on that paragraph, and the function or the file it named further down was never looked up. Past the twelfth candidate it now reads on for names typed as code: an identifier with an underscore or in camelCase that is a symbol’s name, a path that is a file’s. On 700 SWE-bench Pro prompts the files an orientation points at are unchanged, the prompts handed a file of the reference patch go from 569 to 600, and the hook takes the same time. On by default; seed_names_anywhere = false in .vexp/vexp.toml turns it off.
An index the extension built keeps its skeletons. An index built by the daemon, which is every index of someone who has only the editor extension, carried no stamp for its cached skeletons, and the first command that opened it emptied them: the git hooks vexp installs, index --status, savings. run_pipeline then showed each pivot as one line. On a 20,729-symbol index one commit emptied the cache, and four run_pipeline answers went from 7,104, 9,020, 3,310 and 7,519 characters to 4,397, 4,510, 2,236 and 4,262. The stamp is now written with the index, a pivot whose cached skeleton is missing is built from its stored node, and the daemon refills in the background a cache an earlier version emptied.
A project kept under a folder named build is indexed. The built-in ignore names (build, dist, vendor, target, node_modules and the rest) were matched against every part of a file’s absolute path, the folders above the project included. A project kept under a folder with one of those names got an empty index, with nothing saying why: the same tree gave 0 files under a folder named build and 1,110 under a neutral name. The names are now matched below the workspace root only.
Setup asks before it writes for an agent the project only hints at. vexp setup took an empty .github, .windsurf or .devin folder as proof that the project uses GitHub Copilot or Windsurf, and wrote their files without asking. A marker is now something the agent itself reads, its instructions or its rules, not the folder they would live in. A bare folder is a hint: the agent is named, with the command that sets it up, and nothing is written. --agents and the interactive list set a hinted agent up as before.
After an update, every entry points at the new build. The entries your agents start vexp from name a path, and two kinds of path did not survive an update. An entry into the VS Code extension’s folder kept naming the previous version’s folder for as long as it existed, so the agent started the previous server, and lost it when the editor removed the folder. Every start of the extension now moves an entry that is vexp’s own and names an older or a missing folder, in the project and in the user-level files of Claude Code, Codex and Antigravity. The same version in another editor, a newer one, the npm CLI’s entry and a custom launcher are left alone. And where Node comes from Homebrew, setup wrote the path of one build, which the next brew upgrade removes: it now writes the link that outlives the build, /opt/homebrew/bin/node, in MCP entries and in the login item of vexp autostart.
An older daemon is replaced the next time its project is used. A daemon is one long-lived process per project, and the CLI started one only when none answered. After npm install -g vexp-cli@latest every project kept the daemon it had, on the version it had started with, until someone restarted it. The CLI and the MCP server your agents start now compare versions when they are used: an older daemon is restarted with the newer engine, once its index is settled and at most once in ten minutes. A newer daemon is never replaced, and one started by an editor window is left to that window. VEXP_NO_DAEMON_UPGRADE=1 switches it off. In the editor, a window left open across an extension update is offered a reload when a newer version is on disk, starting with the update after this one, and the extension says so when the vexp-cli on the machine is older than it is, with the command that updates it.
vexp daemons shows the process and its memory, and vexp stop --all stops them all. vexp daemons listed every daemon on the machine with its project, version, index size and uptime. It now adds the process id and the memory each one holds, and marks a daemon that runs an editor extension’s engine as that editor’s: such a daemon lives as long as its window and comes back when stopped from a terminal, so for an old one the line sends you to the window instead. vexp stop --all stops every daemon on the machine and says which of them an editor will start again. On macOS a daemon now knows when its program file was replaced or removed under it, as it already did on Linux, and vexp doctor and vexp daemons report it.
Restart Daemon keeps the daemon the window’s, and the sidebar stops asking every ten seconds. The Restart Daemon command of the VS Code extension restarted the daemon detached from the window, so from that click on, closing the window no longer stopped it. It now restarts it as the window’s own, also when the daemon it replaces was started by the CLI, and says “restarted” only when that is what happened. And the sidebar, which re-renders every ten seconds, started a process at every render to read the state of the local LLM, in every window where the panel had been opened, on screen or not. It now asks again only when the answer can have changed: ten minutes with nothing changed are three processes where there were sixty-one, and a hidden panel starts none.
The daemon log holds no word of your prompts. vexp doctor --report quotes the warnings and errors of the daemon log, and the report is meant to hold counts, timings and paths, never your prompts or code. The log held both: seven statements printed the query, the request line was logged by its first 200 bytes, and an error that repeats what was asked was logged whole. The statements now log the query’s shape (characters, words), the request line its size, and such an error its kind. On a replay of every tool with a failing request, 15 warning or error lines held request words; now none does.
Doctor reads an extension-only install as one. Everything an extension-only user runs comes from the editor’s extension folder, and npx vexp-cli doctor brings the newest CLI from npm for one run. On a day when a release reached npm before the Marketplace, doctor read the extension’s own daemon and server as stale installs and printed the advice of a command-line install, down to ending a process that was the editor’s extension host. Doctor now works out what is installed before it advises: a daemon that is the extension’s at another version is not stale, a server the extension owns is one informational line, and a project that is simply not open is not a fault.
The hook sets a subagent’s report aside, and says why a prompt was skipped. A subagent’s hand-back reaches the hook as a prompt, and it was oriented like a question: 1,774 characters in one replay, and one of the session’s orientations. It is now set aside like the agent’s other text. And after two orientations in a row that were ready too late, a session’s long prompts are skipped until one arrives in time. The reason given for it claimed that long prompts run past the budget on this index, which nothing measures; it now says what happened and what ends it.
Switches, for telling a change from a cause. The gate and each of its rules can be turned off for a workspace in .vexp/vexp.toml (seed_gate, seed_expansion_anchor, seed_plain_word_rule, seed_names_anywhere, each set to false), read at every prompt with no restart. For one daemon, these environment variables put back what the engine did before a change: VEXP_SEED_GATE=0, VEXP_SEED_EXPANSION_ANCHOR=0, VEXP_SEED_PLAIN_WORD_RULE=0, VEXP_SEED_NAMES_ANYWHERE=0, VEXP_SEED_CAPSULE=full, VEXP_SKELETON_CACHE=leave. The daemon’s log names the ones it started with. VEXP_SEED_TRACE=1 writes one line per prompt with what the gate decided and, new in this release, where the time went, phase by phase.
Upgrade note: no rebuild, and two commands if your Node comes from Homebrew. No index is rebuilt, with one exception: a project kept under a folder named like a built-in ignore (build, dist, vendor, target and the rest) runs a full index at its first start, because its index was empty. A skeleton cache an earlier version emptied is refilled by the daemon in the background. Update the VS Code extension together with the CLI, and reload each open editor window once. If your Node comes from Homebrew, run vexp setup once after updating, in a project where you use Claude Code, so the entry you already have is rewritten, and vexp autostart install again if you use the login item.