112 guides, sorted by the problem you have. Every one is checked against the app and dated.
10 topics. Pick the one that sounds closest to your problem. Each is split into smaller headings, so you can find the exact guide.
Download, install and open NeuralVault for the first time.
11 guidesMaking an account, signing in, and what your edition includes.
16 guidesYour balance, top-ups, your subscription and what you have spent.
6 guidesWhere your notes live and how to keep them safe.
13 guidesConnecting a model, choosing one, and using a chat day to day.
24 guidesWhat the assistant may do, and how you stay in control.
11 guidesFinding your own notes, and letting the assistant use the web.
5 guidesLink the assistant to tools and services you already use.
8 guidesKeeping the app current, and telling us when it breaks.
15 guidesWhat leaves your machine, and how to remove what is on it.
3 guidesSign-in trouble, a plan that will not activate, a payment question, a device you no longer use. Those are handled in your account rather than through a bug report. The documents that govern all of it are published here too.
There is more than one way to tell us, and none of them needs a GitHub account. Use the form on this site, report from inside the app, email us, or tell us privately if it is a security problem.
Fill in a short form: what happened, what you expected, and how to reach you. No GitHub account, no app open, and no diagnostics attached, so tell us anything that would help us see it.
Open the report formSettings, then General, then About, then Report a bug. The app builds the report and shows you the exact text first, so nothing leaves your machine until you have read it. This is the route worth taking when you can: it is the only one that attaches real diagnostics.
In the current beta it then opens a prefilled issue on our public GitHub tracker, which needs a GitHub account and can be read by anyone. Open a blank issue on GitHub if you would rather file it there yourself.
For a reply from a person, email contact@perpetualtechnologies.co.uk or use the contact form. That route targets two business days, and a real person reads it.
Get in touchTell us directly rather than filing it as an ordinary bug. We will not take legal action against anyone who reports a genuine issue in good faith and gives us a reasonable chance to fix it before going public.
Read the security policy