BooBridge writes what happened and what it learned into files in your project folder when you close a session, and reads them back when you open the next one. That is the whole mechanism. Everything below is detail.
A session has three phases, and you only open and close it. The middle is your ordinary working day.
Loads your project's history, preferences, and past decisions, so Claude is up to speed the moment you begin.
Plan, delegate, analyze, and build. This is where you and Claude do everything from everyday tasks to the bigger jobs.
Saves what you did, records any lessons worth carrying forward, and closes cleanly so the next session opens caught up.
There is nothing to memorize beyond those two phrases.
BooBridge works inside Claude Cowork's project system, so the project comes first. Create a Cowork project and attach a folder. Naming the project and choosing the folder happen in the same dialog, and the folder is not optional: it is where BooBridge keeps your memory and where Claude does the work.
Then open the project, start a chat in it, and say “set up this project” once. BooBridge builds its memory files in the folder. It takes a few seconds and you only do it once. “Create project” and “new project” do the same thing.
After that, every session is a fresh chat in that project, and it starts with “catch up.” Point a new project at a folder that already holds BooBridge memory and catch up resumes that project instead of starting a fresh one.
The folder must be picked here, while the project is being created. One added afterwards lasts only that session.
None of these are required, and all of them are plain English.
Corrections need no phrase at all. When you tell Claude it got something wrong, closing the session is where that lesson gets written down, so the next one starts already knowing it.
BooBridge keeps four kinds of memory. Each one covers a different part of how you work.
How you work and how you decide. Write a few lines yourself if you like, and it fills out on its own from what actually happens in your sessions.
Claude works the way you do without being told every time.
Brief or detailed, formal or plain, when to push back and when to just do the thing. Correct the tone once and the correction sticks.
Less time steering, more time getting work done.
What worked, what went wrong, and the calls you already made. This is the part that turns a mistake into something the project knows.
The same mistake doesn't happen twice.
Decisions, progress, and the turning points that matter, plus the roadmap of what is still open. Saved as you go and again when you close.
Every session starts with the whole history already loaded.
The first three live in one file called House Rules. The project's history and its roadmap live in files of their own beside it. All of them sit in your BooBridge folder as plain text, none of it on a BooBridge server, and you can read, back up, or delete any of it. Two of those files are written by BooBridge itself, so change those by telling Claude rather than editing them by hand.
Claude can talk anything through with you: analysis, ideas, planning, decisions. It is also good at making the thing. Websites, dashboards, lesson plans, presentations, spreadsheets, even audio. Cowork does that work in the session itself, on your machine, in the folder you gave it.
Memory is what makes the second and third attempt better than the first. A one-off build starts from your description alone. A build inside a project that has been running a month starts from your description plus what that month recorded: the file layout, the style you keep asking for, and the approach that already failed once.
Memory is only useful if it is true. A record that drifts out of date is worse than no record, because you act on it.
So closing a session is a checked step, not just a save. Before writing anything, BooBridge looks for claims that no longer match the folder, notes that repeat each other, and a description of the project that has drifted from what is actually in it. Claude settles most of what turns up in the same breath. The rest, where the call is yours, comes to you before the session closes.
The install takes a few minutes: one file to upload and one setting to turn on.
See how to install