Short answers, with a link where the long one lives. If something you need isn't here, ask; the answer usually ends up on this page.
No. Setup is one installer, and Claude Desktop is registered for you (Claude Code and Cursor take one button). After that you talk to your assistant normally: "remember this", "what did we decide?", "forget that". There's nothing to configure and no query language to learn.
Anything that supports MCP, the open standard for connecting tools to assistants. Today that includes Claude Desktop, Claude Code and Cursor, with the list growing. It won't work with an assistant that has no MCP support.
Yes, through a hosted relay: choose Connect to ChatGPT in the ModelBrain menu, add it as a plugin in ChatGPT, and sign in to your free ModelBrain account to pick the computer. It's the one connection that doesn't stay fully local, since ChatGPT on the web can only reach outside tools through an internet-reachable connector. How to connect it.
No. There's no sign-up, no password and no licence key. An account only comes into existence if you connect ChatGPT (free, it needs a sign-in) or subscribe to something that involves our servers.
Now. macOS, Windows and Linux builds are live on the download page. It ships as a beta, and the recall-test scores are published.
In a folder you choose on your own computer. You can move it, copy it or delete it like any other folder. If you delete it, it's gone: there's no copy anywhere else unless you set one up.
No. Not on any tier, not in aggregate, not anonymised. Separately, remember that your assistant is a different company with its own terms; we control what's on your disk, not what Claude or Cursor does with a memory once it's in the conversation.
Local use with Claude Desktop, Claude Code or Cursor: no, we have nothing, since those talk to your local ModelBrain directly. ChatGPT connects through a hosted relay that forwards each request to your computer and back, so it handles the content in transit without writing it to disk. Sync and managed backup: no, they're encrypted before they leave your machine and we don't hold the key. Teams: no, a shared partition is encrypted on each member's computer with a key only the members hold; we see who is in the team, not what's in it. The three modes, in detail.
Not by ModelBrain today; the security statement has the detail. Turn on FileVault, BitLocker or LUKS instead; your operating system already does this well, for free. We do not plan to add one, because the key would have to sit on the same computer.
Every recalled memory comes back with its date and where it came from, so you can check it rather than take its word. Correct it by telling your assistant the new version; the old one becomes history rather than a competing answer.
It stops appearing in every recall at once. For 15 minutes you can bring it back with Undo recent forgets in the menu, and its text is cleared for good after 24 hours for a synced folder and 30 days for a saved memory. That it is gone is a pass/fail line in our own test rather than a promise in marketing copy. "Forget that" takes a mode: revert (the default) tombstones the current version and brings the one before it back as current; object removes just the version you named; chain removes the whole correction history at once. Nothing comes back on its own as a side effect of any other call, only when you explicitly choose revert.
Your assistant asks it to save things, so in practice some of that is the assistant's judgement. What ModelBrain guarantees is that nothing is hidden: everything stored can be listed, checked and deleted by you, and nothing it stores can mark itself private or claim a source it doesn't have.
It won't spot that by itself; we've deliberately not claimed otherwise. You tell it which is current, and the other becomes history you can still look at.
Nothing, for everything on your own computers, permanently. You pay only for things involving someone else's machine: syncing between devices or a shared team collection, plus a flat $0.05 per GB per month for the backup and vault storage those use. Pricing.
Day to day it's idle between requests. The honest exception is the first read of a large folder of documents, which uses real CPU for a while because it processes everything locally instead of sending it away. If you also run another app that keeps its own local model loaded (Ollama, LM Studio and similar), expect some slowdown when both are active at once, since they're drawing on the same CPU, RAM and GPU. Nothing to configure for it, just worth knowing if things feel sluggish.
Whatever your backup habits allow. Your vault is ordinary files, so Time Machine, File History or any backup tool you already run covers it. If you'd rather not think about it, device sync includes managed backup, keeping encrypted restore points and restoring to a new machine in one command; the space the snapshots use is billed at $0.05/GB/month.
Uninstalling stops ModelBrain and removes the program and the entry it added to your assistant's settings. Your vault folder stays where it is, and its path is printed so you can keep it, move it, or delete it. To delete the vault as well, delete that folder yourself (on Linux, run uninstall.sh --purge-data). Because the vault is ordinary files on your computer, deleting it is complete deletion, with nothing left to request from us. Uninstalling does not cancel a paid subscription; cancel that from your account. Details.
Yes. Your vault is a folder on your computer, and since 0.5.1 a command writes every memory out as plain Markdown files (or one JSON Lines file). It needs ModelBrain running and never overwrites anything. From 0.6, --history also writes the earlier versions of memories you replaced. How to run it. If you use sync, Export in the Account window also saves an encrypted copy of what you have synced. We'd rather you could leave easily than rely on it being hard.