Verified purchaser
For coding, not general LLM use, which makes smaller tiers useful for newbie projects
First, and most importantly for most on here, don't assume this will help you token-optimize for anything but coding projects. That's its purpose.
Second, if you've wanted to try "vibe-coding" then this will be of use. And, small projects will require very minimal nodes coverage, but the repos limit will get you. Of course, just delete the vexp file and re-target the new project to untether. For example, I had a really small web with several interactive pages, and it used 41 nodes and had 40 edges. When I started, I targeted my general projects folder where I store work, thinking it would self-configure. It indexed the whole thing and not just the coding projects. That was clearly over 10k nodes, and so I was stuck on updating future use. When I read the docs page, I couldn't find an option to fix it, despite changing folders, etc. Thus, I targeted Opus at the docs page for guidance. It answered and the fix was produced.
Third, If you think your future entails more coding - or local agents that use your token subs - then this is worth considering to manage those future costs. If you get 15% more throughout per session, given your monthly/annual plan costs, then what's the ROI expectation after a year?
Finally, the setup and adjustment is seemingly simple with VS Code - if you know where to go to find the right instructions. One star off because I found some of this out through reading, trial, and error, not through this AppSumo page or the installation page guidance.
Nicola_Vexp
Jul 26, 2026Thank you, this is a genuinely useful and generous review, and I appreciate you laying it out so clearly, especially the part explaining that vexp is for coding, not general LLM use. That distinction trips people up, and you framed it really well.
Sorry you hit some friction getting there, pointing it at your general projects folder and having it index everything past the node limit is exactly the kind of early snag we want to smooth out, and making that first experience more intuitive is something we’re actively working on. You clearly worked it out well, retargeting to the specific project is the right move, and the node and repo mechanics you described are spot on.
We really appreciate the honest, detailed write-up. Feedback like yours is exactly what helps us keep improving the experience, so thank you for taking the time.