Vexp Review (2026): Does It Really Save 70% of Your Tokens?

1What is Vexp?

Under the hood, Vexp uses tree-sitter to turn your code into a graph: functions, classes and types become nodes, calls and imports become edges. Everything is stored in a local SQLite file. Secrets are filtered out by default and nothing is uploaded (vexp.dev [1]).

When the agent asks for context, Vexp searches the graph and returns “pivot” files in full, with neighbouring code reduced to signatures. The maker quotes a full index in under 15 seconds and queries in under half a second. One buyer confirmed the speed: about 900 TypeScript files indexed in under 30 seconds (AppSumo reviews [5]).

Vexp exposes 12 MCP tools. The main one runs context search, impact analysis and memory recall in a single call. Others show the “blast radius” of a change, trace a call path between two functions, and check the agent’s work before it says it is done. It works with 17 agents, including Claude Code, Cursor, Windsurf, Copilot, Codex and Zed.

The company is young. Vexp was founded in February 2026 in Milan, Italy, and is a bootstrapped team of 1–10 people led by founder Nicola Alessi, according to its AppSumo profile. Local-first privacy is a theme we like on Spineye, from note-takers like Prismical to the lessons in our Huntarr security incident piece about trusting tools with your data.

2How much does Vexp really save?

The difference matters. Vexp’s savings counter answers the question “how much smaller is this context than the files it replaces?” It cannot see whether the agent then reads those files anyway. The v3.0 test answers a different question: what did the whole session cost? In that test, sessions with Vexp also solved more tasks, 24 of 25 against 22 of 25 (VS Marketplace [3]).

The buyer who measured it himself

The most useful review on AppSumo comes from a Tier 4 buyer who spent two days measuring Vexp in Claude Code. In four sessions, Claude Code called a Vexp tool only once, after he added an instruction to CLAUDE.md. That session used 71% more tokens than the same task without Vexp.

“If you are comparing tools, do not use that percentage as your evidence — measure your own sessions.”— thomklin, Tier 4 buyer, AppSumo review [5], August 2026

His explanation is fair to both sides. Claude Code already ships its own search tools and reaches for them first, so the two overlap. He also found that setup did not install the Claude Code hook that should inject context automatically. The founder replied within a day, called the missing hook a real defect and says it is fixed. The reviewer concluded that Vexp suits editors without strong built-in code search better, such as Copilot, Continue and Cursor.

The benchmark on Vexp’s site needs the same care. Claude Code with Opus 5 and Vexp resolved 81.7% of 731 SWE-bench Pro tasks at $1.52 per task. Vexp itself notes that no run without Vexp was published on the same setup, so its own contribution is not isolated (Vexp benchmark [2]).

3How to reduce Claude Code token usage (with or without Vexp)

Anthropic says the average Claude Code user spends about $13 per active day and $150–250 a month. Nine in ten users stay below $30 per active day (Anthropic cost guide). These steps come from that guide, plus the lesson from the Vexp measurements above.

1. Measure first. Note what a typical task costs today, from your usage data or session transcript. Do not rely on a plugin’s own savings counter, as the AppSumo reviewer showed.
2. Use /clear between unrelated tasks. Old context is replayed on every turn, so starting fresh is the cheapest saving there is.
3. Compact with a focus. Tell /compact what to keep, for example “focus on code samples and API usage”, so the summary stays useful.
4. Keep CLAUDE.md under about 200 lines. Move specialised instructions into skills that load only when needed.
5. Switch off MCP servers you are not using. Check them with /mcp, and prefer command-line tools when they do the same job.
6. Hand verbose work to subagents. Their long output stays in their own context; only a summary returns to your main session. Simple subagent tasks can run on a cheaper model such as Haiku.
7. Then consider a context engine. Tools like Vexp or Serena help most in large, existing codebases. For a new project, a Reddit commenter in r/ClaudeCode notes that clear planning up front saves more (Reddit).
8. Check that the agent actually calls it. If you add Vexp to Claude Code, confirm in the transcript that its tools are used, and compare the cost with your baseline from step 1.

The same “measure, then decide” logic runs through our Honeylog review, where server logs show what AI crawlers really do rather than what dashboards suggest.

4What do users say about Vexp?

The positive reviews quote the savings counter often: 77% over 17 calls, around 88% over a weekend, 62% on a 4,500-node repo. One API user reports about 30% lower costs in a week. Others praise impact analysis, with one buyer saying it “finds bugs that text search realistically cannot”. Several single out the founder’s support, including a free seven-day unlimited trial for one enterprise tester (AppSumo reviews [5]).

The criticism

Apart from the Claude Code measurement above, two issues stand out. A two-taco review from September says the “10 seats” of Tier 4 share a single licence key that cannot be rotated or revoked. In practice, a former employee could keep using a paid seat. A four-taco review warns that Vexp is for coding only: pointing it at a general projects folder blew past the node limit, and the documentation did not explain the fix. On the VS Code Marketplace the extension scores 5 out of 5 from 20 ratings, with 3,978 installs; Vexp itself counts 33,000+ installs across all channels.

If you run AI agents on your own infrastructure, our jurniti review covers the hosting side, and our Accordio review looks at a back office built around Claude. Before you ship what your agent built, our Vibe App Scanner review explains what to check for security.

5How much does Vexp cost in 2026?

Source: AppSumo, checked 25 September 2026. Tiers 1–2 receive future Pro updates, Tiers 3–4 future Team updates.

The plan cards also show smaller differences. Tier 1 lacks the shared workspace and git index, and Tiers 1 and 2 lack priority paths and analytics. Intent detection, the LSP bridge and session memory are included on every tier.

A node is one function, class or type, so the node count measures how big a project is. Individual projects are unlimited on every tier; the repo limit only applies to repositories linked in one workspace. The maker’s advice is to run the free plan first and watch the node count. For comparison, the free Starter plan covers up to 2,000 nodes and 20 calls a day, and Pro allows 50,000 nodes and 1,000 tool calls a day (vexp.dev [1]).

6Vexp vs Serena vs Claude Context

Sources: vexp.dev [1], Serena on GitHub [8], Claude Context on GitHub [9], checked 25 September 2026.

Serena has 29.8k GitHub stars and works with Claude Code, Codex, Cursor and JetBrains IDEs. It is the natural first try for anyone who prefers open source. Claude Context has 12.6k stars; its trade-off is that your code is embedded through an external service unless you run those parts yourself. Vexp sits between them: closed source and paid, but local, with a free tier to test on. Finding small, capable tools like these is what our hidden-gem software research is about.

7Vexp pros and cons

8Who should buy Vexp?

The honest summary of this Vexp review: the engine is real, fast and private, and the team is unusually open about its own weak spots. The big percentages, though, describe smaller answers, not smaller bills. At $49 with a 60-day refund, the sensible move is to test it the way the most careful reviewer did. Measure a normal week without Vexp, then with it, and keep it only if your own numbers improve.

Good fit: developers on large, legacy or multi-repo projects; teams paying per token through an API; Cursor, Copilot and Continue users. Poor fit: greenfield projects, casual users on flat-rate plans, and teams that need per-user licence control today. For other small-team tools we have tested the claims of, see our Nuwtonic and TubeOnAI reviews.