Your context shouldn'tbelong to one vendor.
The tools you use will change. What you've built up with them, your history, your memory, your instructions and your services, shouldn't have to start over each time.
Context piles upin whichever app you were using
Switching AI tools is easy until you have used one for a while. What you've built up with it stays behind.
Your history
The conversation where you worked out the migration is in one app, in that app's format. A different tool can't read it, and you can't search both at once.
Your memory
What a tool has learned about how you work lives in that tool's memory, under that vendor's rules. It doesn't follow you to the next one.
Your instructions
The same preferences get copied into a file or a settings box in every tool, and drift apart.
Your agents
Steering a coding agent from your phone usually means using that vendor's own app, and only that vendor's agent.
Keep it outside the toolsand let every tool reach it
0bridge holds the shared parts, in plain forms, behind one open protocol. Each tool stays free to be replaced.
Services, once
Sign in to Linear, Notion or Slack one time. Every tool you use calls them through the same MCP endpoint, so changing tools doesn't mean signing in again.
Sessions you can resume
Your coding sessions are collected into one searchable place, and a short reference like 0b:k3f9x2 continues one in a different tool. Resume anywhere
Profile, memory and skills
Plain Markdown and short notes, readable by every AI you connect. Your profile, instructions and skills are kept on your machine as files too; memory lives on 0bridge. How it works
Agents through any client
Start and steer Claude Code and Codex on your own machine from Claude, ChatGPT or the dashboard, on the machines where you turn it on. Your agents from your phone
An open session format
The schema, 0b.session/1, and the converters that read each tool's logs are a package under the Apache 2.0 license. 0bridge keeps a searchable index of the conversation, not the full log. The source
You can leaveand take it with you
A tool that holds your context should make leaving easy. Here is what that means for 0bridge.
Your files stay yours
The sessions your tools wrote are still on your machines, as they wrote them. 0bridge's copy of them is an index for searching and handing off. Your profile, instructions and skills are Markdown files that 0b context keeps in sync; they remain on your disks. Memory, chats saved with bridge__session_save and Claude Code on the web sessions live only on 0bridge and go with your account.
Delete the server's copy
Deleting your account in the dashboard deletes your connections, vault, history, files, profile, memory, skills and agent data. Disconnecting a service deletes its tokens at once.
An open protocol
MCP isn't ours. Any client that speaks it can use your endpoint, and a different endpoint can replace ours.
A client you can read
The 0b CLI, and the code that encrypts your vault, is source available under the Functional Source License, which becomes Apache 2.0 two years after each release.
What we don't claimso you can weigh it
0bridge is a dependency too, and we'd rather say where the edges are.
About the format
- The session format is not a standard. We won't call it one until at least two other tools use it. It maps to other formats, and some of that mapping loses detail.
- The service is hosted and not open source. Only your vault and personal files are sealed from it.
About the clients
- Not every AI product lets you add a server. We list which ones work, which take a token, and which we haven't tried, with the date. Supported clients
- A vendor's own chat history and built-in memory stay in that vendor's app. We can't import them; you can use the vendor's export.
- Chat apps don't see your coding history unless you turn that on.