Straight answers to the questions people ask before they install.
For a one-off question, you do not. Claude carries some memory of its own and can look back over a long conversation.
It runs out when you work on the same thing for weeks. Building something means a pile of small decisions, dead ends, and preferences that only pay off if they are still there tomorrow. BooBridge keeps that pile as files in your project folder and loads it at the start of every session. The difference shows up on day ten, not day one.
No. It is independent, and you install it yourself by uploading the file. Inside the zip are ordinary Python scripts and the rules they follow, written in plain English, so you can open it and see what it does.
Pretty much, yes. BooBridge was built with Claude, by someone who uses it every day, not by a software company. Nobody is claiming it is amazing software.
It is built well for what it is. Every release runs its own test suite first, and the project's own memory is kept by the plugin itself, so anything broken shows up on me before it shows up on you. Writes to your files go one at a time, and each one is read back to confirm it landed.
It is free, it is plain text you can read, and it is useful right now. That is the offer.
On your own computer, as plain text files in a folder you choose. Nothing is uploaded to a BooBridge server, because there isn't one. Your conversations with Claude still run through Claude the way they always do. BooBridge only adds the local memory.
Check the folder first. BooBridge keeps your memory in the folder you attach, and the folder has to be picked while the project is being created. One added to a project that already exists lasts only that session, and that is the most common reason it does not work on day one. Here is where to pick it.
If the folder is right, restart Claude, and restart the computer if it is still odd. Claude sets up a small workspace in the background, and on a brand-new install it is sometimes not ready. The errors you get then sound technical and have nothing to do with what you asked for. A restart clears it.
Claude does the work in its own workspace, which may be on your computer or in Claude's cloud. Either way your memory lives as plain files in the folder you attached, and that folder is the real copy. BooBridge reads those files when a session opens and writes them back when it closes. You do not have to set anything for this.
The folder was probably attached after the project already existed, and that kind only lasts one session. A folder picked while the project is being created stays attached for good. Here is where to pick it.
Your memory files are fine either way. Make a new project, attach that same folder while you create it, then start a Cowork chat there and say “catch up.” It picks up where you left off.
Nothing. No tier, no trial, no account. If it saves you time and you feel like saying thanks, there's a donation option, but it's never expected.
Remove the plugin whenever you like. Your memory files stay where they are, because they are just files in a folder. Nothing is trapped inside BooBridge.
BooBridge probably has a finite shelf-life, and that's fine. The model vendors will likely build memory and workflow features like these into their products before long, and there are sharper developers with more time who could build something tighter. None of that changes the fact that it's useful right now. Use it while it earns its place.