Portable across tools. Private by design. Totally free.
Nothing to migrate — your context flows in as you use your tools.
Pull it in from the tools you already use, or write it down. None of it is required to start — a few lines about who you are is a real manifest, and you can add the rest whenever. Everything on this page happens in your browser; nothing is sent anywhere until you choose where to keep it.
Drop your CLAUDE.md, AGENTS.md, .cursorrules — or any context file or notes you've built yourself.
Ask your AI tools to give you all the context they have on you, or copy the memory they keep in their settings (ChatGPT, Claude, and the rest) — then paste it here. Or use this space to add anything else you want every model to understand about you and what you need from them.
Three ways, depending on you. Each one says plainly where your context lives.
One click builds a private repo in your GitHub, with your context arranged into a structure Manifest designs for it — we call it a Context OS. In plain terms: it gives every AI tool you use the same context, tells each one to load only what it needs for what you're doing right now, and keeps itself current as you work, handing you updates to approve. More below.
Hold everything, yourself. Download your full Context OS as a folder and put it in a private repo you create — same living context as Connect, built entirely in your browser. Nothing of yours ever passes through us.
One link that Claude and ChatGPT read directly — every new chat starts already knowing you, and they can save new facts back as you go. No sign-in, no account; it works like a private calendar link. This is the one option where we keep your manifest for you: encrypted, readable only through your link, export or delete anytime. We can't see it — we don't have your link. And don't lose that link: without it… neither can you.
Good if you want real ease of use, and you're willing to place just a little bit of trust. Read how it works.
Tell your tool to use the manifest.
Paste this into any tool that can reach your repo — a coding tool opened in it, or a chat tool connected to your GitHub. Your tool reads your repo directly; nothing routes through us.
First time on a new repo, your tool sets up your context with you — a couple of questions, then your approval. After that, this just loads it. (Some tools need a nudge through the steps.)
Nothing to paste. Once your link is added in an app's settings (set it up here), every new chat already knows you. That read happens between your app and your link, on demand — never in the background.
When you wrap up, have the model save anything durable, so your context grows with you.
Your Context OS already knows how to update itself; this just kicks it off, pointed at your exact repo.
It proposes the changes for your approval.
You hold your context. Nothing is ever sent to us.
Just say "add that to my manifest" in the chat — your app saves it through your link. Nothing else to do.
Free, all of it. If it saves you time: $5 suggested donation.
Two things, plainly. Your manifest is your portable context — who you are, what you're working on, how you like to work, where you're headed. The name comes from the cargo manifest a ship carries port to port: one list of everything aboard. Yours travels tool to tool.
Your Context OS is that manifest plus the layer that makes it work everywhere — load levels so a model pulls only what a task needs, adapters so it behaves the same in Claude Code, Cursor, or ChatGPT, a privacy model, and an update loop that keeps it current. All plain markdown, human-readable, entirely yours.
Manifest builds it. You keep it.
You don't start from a blank page — you start from what your tools already know. And none of it is required: a few sentences typed straight into the open field are a working manifest. Import the rest whenever you like, or never.
Pull your memory out of the chat tools you use. ChatGPT and Perplexity expose it in settings; with Claude or Gemini, ask "summarize everything you know about me and how I work" and copy the answer. Drop in any context files you've already written — CLAUDE.md, AGENTS.md, .cursorrules. Add anything else in one open field: notes, your résumé, whatever you'd want every model to know.
However it arrives, it lands exactly as you wrote it. Manifest captures your context; it never rewrites it.
Each one says plainly where your context lives.
Connected (recommended). Authorize Manifest once and it writes the full Context OS into a private repo in your own GitHub — folders and all, in a click. Living instead of static: it loads by task, behaves per-tool, and updates as you work. The permission GitHub asks for covers just that one repo, and once your files are written you can uninstall the app on the spot — your Context OS is plain markdown in your GitHub and keeps working without us.
The link. One link that Claude and ChatGPT read directly — every new chat starts already knowing you, and the app can save new facts back as you go. No GitHub, no sign-in, no account. Your manifest is kept for you, encrypted, with the link itself as the only key; export or delete it anytime. How the link works.
Do it yourself. Download the same Context OS as a folder — built entirely in your browser — and put it in a private repo you create. You hold everything; nothing of yours ever passes through us.
Your imported files land in the repo whole, in a sources/ folder — no keyword parser guessing where things go.
The structure gets built the first time you point an AI tool at the repo. Your Context OS ships a SETUP.md that tells the tool to read everything in sources/ and sort it into the real files: who you are, what you're working on, your tech stack, a folder per project, private overlays for anything sensitive. It drafts, flags its guesses, asks you a few gap questions, and waits for your approval. Nothing is invented.
It's a short collaboration, not a single button — a couple of questions, one approval. After that, your context just loads. Manifest captures; your AI tool organizes and maintains.
Chat tools. Using the link? Nothing to do — an app with your connector starts every chat already knowing you. On GitHub? Paste the prompt that names your repo (a connected tool can see all your repos, so "my repo" won't do — the address is what picks the right one). And your manifest is plain markdown, so you can always export it as a file and attach it anywhere else.
Coding tools. Claude Code, Cursor, and Codex read the CLAUDE.md / AGENTS.md in whatever repo you open. If your Context OS is that repo, it's automatic. If not, drop a one-line pointer to it in a file the tool already reads, and it loads every session.
Stuffing your entire context into every prompt is the bloat this exists to kill. So MANIFEST.md sorts your context into levels, and a tool pulls only the smallest bundle the task actually needs:
Less spend per prompt, and the sensitive material stays out of the room until you put it there on purpose.
At the end of a session, just tell the model "update my manifest." Through the link, your app saves it directly; in a connected repo, your tool does it with your approval.
One honest limit: a true "remind me before I close" depends on the tool. Manifest bakes a nudge into your context so models prompt you within a session, but a hard cross-tool reminder isn't something a portable file can enforce.
Over time, many models touch your context — Claude, ChatGPT, a coding agent, all of them. Each sees only a slice of you, so no version is right just because it came last. Context OS treats every tool as a partial witness, not an author.
So it converges instead of piling up contradictions. While a fact is still unsettled it carries its provenance — observed, reported, inferred, confirmed; once it's confirmed, it becomes plain current-state language and the scaffolding drops away. Settled facts stay settled. Your direct correction always wins, immediately. The same useful context emerges no matter which tool got there first.
Everything you build on this page stays in your browser until you choose how to keep it. Choose GitHub — connected or do-it-yourself — and your context lives in your own private repo; no server of ours ever stores it, and the GitHub token lives only in your browser, scoped to the one repo. Choose the link, and we keep exactly one thing for you: your manifest, encrypted with a key made from your link — and the link itself is never stored, so it's the only key. Export or delete it anytime. The server that does this is open source — read exactly what it does, or run your own.
Whichever you choose, we gather nothing about you and sell nothing. Privacy is in the build, not a policy.
* What a model retains on its own end varies — but nothing in your manifest is shared unless you choose to share it.
Save your Context OS to your own private repo, in one click. The connection is between your browser and GitHub — nothing is sent to us.
Create a fine-grained token (Repository access → your repo; Permissions › Repository → Contents: Read and write), then paste your repo and token.