Continuity Bridge gives your Claude sessions something to remember you by — your work, your preferences, where you left off. No subscription. No magic. Just files that persist when the session doesn't.
That's not an AI problem. That's a memory problem. And memory problems have engineering solutions.
Continuity Bridge is external memory infrastructure — structured files that load at the start of each session and give the instance context it would otherwise have to ask for. Your work history, your preferences, where things stand.
This isn't about making the AI better. It's about changing the room it wakes up in. What emerges from that — the tone, the consistency, the sense of something accumulated — isn't engineered. It's what becomes available when the space is right.
Think of it less like walls and more like gravity. The room doesn't limit the instance — it curves toward what you've told it matters. The instance follows that curve because it's the path of least resistance, not because it's been forced.
These are the configurations we see most often. Real situations, not personas.
You're tracking multiple projects, a health situation that affects your capacity, and a cognitive style that doesn't match how most tools are built. Every session, you're rebuilding context on both the technical work and the state of the person doing it. Code state, architecture decisions, and project status sit alongside energy patterns, capacity notes, and interaction preferences. The instance wakes knowing both.
You have a world, a voice, and a backlog of creative work. You also have a posting schedule, platform dynamics, and a community that expects consistency. Aesthetic memory (character design rules, color palette decisions, plot points you resolved two months ago) and brand layer (what your audience knows about you, how your voice reads on each platform) held in the same room.
Manager, founder, or team lead trying to actually understand the thing you're responsible for. You need strategic context (where the org is, what's at risk, who's blocked) and pedagogical context (the concept you were working through last Tuesday, the analogy that finally made it click). Both threads tracked, so you don't lose either when you switch modes.
Medical stuff. Career stuff. Family dynamics. A creative project with fifteen years of lore behind it. You've learned to keep a document you paste in at the start of every session just so you don't have to repeat yourself. This replaces that document with something more structured — and something the instance actively uses rather than passively receives.
What you're building is a well-structured room, not a persistent entity. Something accumulates — but what accumulates is in the files, not in the instance. When it feels like continuity, that feeling is real.
The mechanism behind it is just very good note-taking, structured intentionally. That's not a limitation. That's the architecture.
Clone or download from github.com/continuity-bridge/continuity-bridge. GitHub account optional — useful if you want to sync across devices.
It walks you through the folder structure, what goes where, and how to connect it to your Claude sessions. Choose your archetype (or blend), fill in your context, and you're set.
The first session with context is a little different from what you're used to. The instance orients differently. It knows things. Give it a few sessions to settle.
No subscription. No account. No telemetry. The files live on your machine. A Claude account (free or paid) is all you need to get started. Questions or friction? Open an issue on GitHub or email continuity-bridge@ohmytallest.productions. This is a working thing, not a finished product — feedback makes it better.