An estate record of every project, product, session and account on your computer. Independent of the app, the login and the subscription. It keeps itself.
What's inside those sessions is not chat. It's the afternoon the thing finally clicked. The three weeks of decisions you no longer remember making. The product you finished and forgot you finished.
You did that work when it was working. On inspiration. That is not on demand. You cannot order the same afternoon twice, and the version that lives in the session is the only version there is.
And the only reader for it is an app that indexes by login, empties its sidebar after a re-auth or an update or an account switch, and closes entirely the day you stop paying.
And here is the floor. Best case, it takes a skilled person a few days to get back to a working place: find the files, move records between account folders, work out what was where, prove what survived. That is the best case. It assumes you have that person, and it still does not give you back the state you were in.
The subscription is the cheap part. The work is the estate. And like every kind of insurance, nobody wants it until the evening they need it. If that evening is today, this page is the fastest way to end it. If it is not yet, this is the cheapest day to buy.
None of this is your fault. The app was never built to answer "what do I have, and is it all still here?"
ConversationKeep reads what the Claude desktop app and Claude Code already write to your disk, every account, every folder, every Claude-tab session, and keeps its own record of all of it: a ledger that never drops a session, a copy of every transcript, and an inventory of the things you are building, found from their own files. Then it draws the whole estate as one map. It runs every time a Claude session starts or ends. You never run anything.
What exists are pieces, and all of them are for developers: a terminal session browser, a history viewer with a backup button, a fuzzy-search script. Every one is single-account, Code-only, and needs a terminal. Nothing else reads the desktop app's own session index, covers Cowork alongside Code, tells you which account a session belongs to, finds the products you built, keeps copies of your published pages, or installs with one click for someone who has never opened a terminal.
The nearest thing to a fix for the account problem is a blog post that tells you to quit the app and move record files between folders by hand. The problem itself is real enough to have at least six separate threads on Anthropic's own issue tracker: sidebars emptied by a re-login, an update, a plan change, an account switch, and one where the content was never saved at all.
It is not a better search box. The desktop app already searches inside your conversations: press Ctrl+K and type. It's good. ConversationKeep's search exists for the moments that box can't reach: the other account's sessions, sessions the app no longer lists, or a day when you have no working app at all.
It won't let you continue a conversation without a plan. It reads, maps and searches everything you did. Picking a session back up still needs Claude.
It won't reach chats on claude.ai in a browser. Those live on Anthropic's servers, not your disk. ConversationKeep is for the desktop app and Claude Code, where the transcripts are yours to read.
It won't change any usage limit, and it won't sync to the cloud or phone home. It reads local files and writes local files. That's the whole point.
It's not signed with a code-signing certificate yet, so Windows will show a "protected your PC" screen the first time. Click More info → Run anyway. The installer tells you exactly what it touches: its own folder, two lines in Claude's settings, a shortcut.
Install it, run it for a month. If it didn't give you a record you trust more than the sidebar, email hello@conversationkeep.com and you get every dollar back. No form, no questions.
Because it's priced against the work, not the app. The work you did with Claude cost you hours you can't get back and a state you can't summon on purpose. The subscription that produced it costs $100 to $200 a month. The best-case recovery without a record is a skilled person for a few days, which at any hourly rate is more than this costs for years. $149 a year is under a week of the subscription, and it pays for the one thing a local record needs to stay true: someone keeping it working as the app changes the files underneath it.
Nothing breaks. The program is on your computer and keeps recording and opening your map. You stop receiving updates, so if the app changes its file layout after that, the record may need a newer version to keep up. Your history is plain files in your own folder either way.
Not in this form. There are free developer tools that browse or back up Claude Code sessions from a terminal, one account at a time, Code only. There is the app's own search, for the account you are signed into. And there is the manual fix: moving files between account folders by hand. ConversationKeep is the only thing that does the whole job, for both accounts and both kinds of session, with the products and the published pages included, and that a person can install in a minute.
Yes. Ctrl+K in the desktop app searches inside your conversations for the account you're signed into, and it's good. ConversationKeep isn't competing with it. It's the record underneath: what to fall back on when that account is the wrong one, has lapsed, or has stopped listing the session you need.
No. It reads local files and writes local files, in its own folder. There is no account, no server, no telemetry. The small local server it runs listens on your own machine only.
They are listed under the project they belong to, with the account that published them, because a published page opens only from that account. Say "archive my pages" in a Claude session on that account and the record keeps a copy of each one, which opens from the map with no login at all. The copy is the page as published; a page that is really an app with a database behind it opens as its shell.
No. Those never touch your computer. ConversationKeep covers the Claude desktop app (Code and Claude-tab sessions) and Claude Code in a terminal, because those write transcripts to your disk.
It puts the program in its own folder, adds two lines to Claude's settings so the record updates at session start and end, raises Claude Code's terminal transcript retention from 30 days to 10 years, installs a small Claude skill, and makes a shortcut. Each of those is a checkbox you can untick. Uninstall from Installed apps puts them all back and leaves your history for you.
The installer isn't code-signed yet, so Windows shows that screen for any new program. Click More info, then Run anyway. If that bothers you, the source is public on GitHub and you can read every line it runs.
Yes. It shows which account each session was born on, warns when the app is on a different one, and can mirror every session into every account's sidebar. The mirror is a checkbox and can be undone at any time. It does not change any account's limits.
Not yet. The code is written for it but untested. Email hello@conversationkeep.com and you'll hear the day it ships.
30 days, every dollar, one email. You don't have to explain.
Not the $200 a month. A few days of a skilled person just to get back to where you were, if you have one. And the hours, the decisions, the afternoon it clicked, which nobody can get back. You can keep trusting an index that belongs to whichever login is signed in today. Or you can keep the estate.
P.S. The cost of waiting is not the price. It's the next session you do in the right state, with nothing keeping it but a sidebar. That state is not on demand.