ConversationKeep · for Cowork and Code in the Claude desktop app, on Windows · your Chat tab chats too, from Claude's export

Everything you built with Claude. Kept. Still yours.

Every Cowork task and Code session you have ever run, from every Claude account, kept on your own computer and drawn as one map you can search, read and pick back up from. Open it and carry on where you left off. See what you did this week, every decision you made, and the whole story of every file Claude changed. It keeps itself current, with nothing to remember. Independent of the app, the login and the subscription.

Not on sale yet $149 / year

Windows · one click, no Python, no terminal · no conversation is sent over the internet

✓ Reads local files only ✓ Keeps itself current ✓ 30-day refund

ConversationKeep: the Map view, with things you are building, every project and every session, and which account the app is on

Your work, drawn as a map. The things you built at the top, every project and session under them.

What it does for you

Your whole history with Claude, working for you.

✓Since you last looked. The map opens with what happened while you were away: runs that started by themselves, what you decided, stories that moved on, anything Claude lost. One press shows it all; it fits your phone too.
✓Pick up where you left off. The top of the map shows the latest conversation of every project you worked on in the last 30 days. Continue opens it in the Claude desktop app; Terminal carries it on in its own folder with everything it had.
✓Find anything you ever said, on any account. Press Ctrl+K on any page and search inside every conversation at once, including the ones Claude stopped listing. Narrow it by Code, Cowork or chats, account, dates or who said it, and land on the exact message.
✓This week, at a glance. For each project: how many conversations, which files changed, what you decided, and Claude's last words, which are usually where the work stands. Written from the conversations themselves: nothing guessed, no AI writing it.
✓Every decision you made. Every yes, no and "from now on" you typed to Claude, with the question it answered and a button to the message.
✓A file's whole story. Every change Claude made to a file, across all your conversations, oldest to newest, and which conversation made it.
✓Nothing lost. A session the app stops listing, or that Claude deletes after 30 days, stays here word for word. Put it back returns a deleted Code session to Claude so you can open it again.
✓One story across handoffs. When a session hands off and a fresh one carries on from its handoff file, they show as one story, "Part 2 of 3" on each. Read every part in order on one page; Pick up opens the newest part.
✓The rules you've set, in one place. Every "from now on", "always" and "never" you typed, under the project where you said it, with a link to where you said it. One press adds a rule to that project's CLAUDE.md, so Claude reads it at the start of every session there.
✓Ask your own history. Type a question about your own work and get a short answer with a link to each message it came from, or "Not found in your sessions." It never guesses. Off until you switch it on.
✓Read it on your phone. Turn it on, pick a passcode, point your phone at the square code, and read and search everything from the sofa, over your own home Wi-Fi.

A session is one conversation; its transcript is the file where Claude writes it down, word for word, on your computer. ConversationKeep keeps a copy of each one.

The work is not the subscription.

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. My estimate: 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 what you made. And like every kind of insurance, nobody wants it until the evening they need it. If that evening is today: the transcripts are usually still on your disk. If it is not yet, this is the cheapest day to get ready.

What you've been told

Three things that aren't true.

"If it's not in the sidebar, it's gone."

The sidebar is one account's index. Your transcripts are on your computer, shared by every account, and the app only ever shows you one login's view of them.

"I can always redo it."

You can redo the typing. You cannot redo the state you were in. Inspired work is not reproducible, and the transcript is the only place the reasoning was ever written down.

"Claude keeps it for me."

The app keeps an index for the account that's signed in, and reading it needs a paid plan. Emptied sidebars and missing content are issues on Anthropic's own tracker. The files are yours. The reader is not.

None of this is your fault. The app was never built to answer "what do I have, and is it all still here?"

The turn

A record the app doesn't own.

ConversationKeep reads what the Claude desktop app and Claude Code already write to your disk, every account, every folder, every Cowork task, and keeps its own record of all of it: every session it has ever seen, even after the app stops listing it, a copy of every transcript, and the things you are building, found from their own files. Then it draws it all as one map. It updates once an hour, every time a Code session starts or ends, and every time you open it. You never run anything. Your ordinary chats join the same record, searchable the same way, whenever you add Claude's export.

If the app forgets, the sidebar empties, the login changes, or the subscription ends, your record is still there. Still readable. Still yours.

How it works

Install once. It keeps from then on.

Run the installer.One file. It finds your Cowork tasks and Code sessions, shows you every change it will make (each one you can say no to is a checkbox), and makes your first copy in about a minute (a few minutes on a big history).

It records.A note of every session it has ever seen, a copy of every transcript, and Claude Code's 30-day cleanup turned into 10 years. A session the app stops listing stays on the record.

It finds what you built.Pages and products you made, found from their own files, with a snapshot, at the top of the map. In the tree every project opens into two folders: its Sessions, each with a one-click Desktop button that opens it in the Claude app, and its Assets: the file to read first, the products and their files, what Cowork tasks delivered, and the pages it published.

It knows which account.Which login each session was born on, a plain banner when the app is on the other one, and an optional mirror so every login's sidebar shows everything.

It keeps up.Updated once an hour and after you sign in to Windows (a small scheduled task, low priority, no window), at every Code session start and end, and whenever you open it. So Cowork tasks are kept with nothing to remember. A health card says green, amber or red, warns you if a Claude update stops it keeping things, and tells you when a session vanishes from Claude's sidebar, with a Windows notification (made on your PC) the first time. Maintained through the year as the app changes the files underneath it. That is what the year buys.

Your chats, when you want them.In Claude, Settings → Privacy → Export data; Claude emails you a link to a .zip. In ConversationKeep, open Chats, press Add my chats and pick it. Adding a newer export later updates changed chats, never doubles one, and never removes one the newer export leaves out.

ConversationKeep: the Tree view, one project opened into its Sessions folder and its Assets folder

The tree. One project, its sessions, its assets. Every link checked against the disk at every rebuild.

ConversationKeep searching for 'overdue invoice' and finding a July conversation from the other Claude account, with the matching messages highlighted

A search for "overdue invoice" finds a July conversation, on the other account, by what was said in it. (Sample data, real program.)

What's included

Everything, in one record.

✓The record. Every session it has ever seen, never forgotten, a copy of every transcript, and Claude Code's 30-day cleanup raised to 10 years.
✓Your ordinary chats, from Claude's export. Add the file Claude emails you and every chat in it is kept, searchable and readable with no login, labelled by account, up to that export.
✓What you are building. Pages and products, found from their own files, with a snapshot and a button to the page.
✓The map. Map, Tree, Table and Timeline of every project, session and product, in a window of its own. Any session opens in the Claude desktop app with one click.
✓Your published pages, kept. A page published on claude.ai opens only from the account that published it. The record keeps a copy that opens with no account, and tells you which login the live page needs.
✓No dead ends. Every file, page, product and deliverable on the map is checked against your disk at every rebuild. Anything moved or deleted is marked missing instead of failing silently.
✓Two-account sanity. Born-on login per session, a banner when the app is on the wrong one, and the mirror.
✓Claude knows where it is. A status line at the top of every new Code session tells Claude which account it is on and which tools it started with. Full, Short or Off, your choice (what it says is under "What does the installer change?").
✓Pick up, put back. Continue any recent project in the Claude app or a terminal, and return a Code session Claude deleted so it opens again.
✓This week, Decisions, Files and Usage. Where each project stands, every ruling you gave, every change to every file, and how much each project and account used, week by week.
✓Your own tags. Group conversations under your own words, like "taxes" or "website", and see them together.
✓Renamed a folder? One button joins the old project's conversations to the new name, everywhere on the map.
✓Easy on the eyes. Light or dark, Ctrl+K search from any page, and two conversations side by side.
✓Save and copy. Copy all, copy one answer or one code block, or save a conversation as Markdown, Word, plain text or PDF. Your notes and pinned messages go into the file too.
✓What Claude did. In Read, the commands Claude ran and the files it read, edited or wrote, with what came back, as folded steps in plain words. Files in the project are named from its folder (src\app.py), so a pasted step doesn't carry your user name.
✓Stars, notes and pins. Star a conversation, write your own note on it, or pin one answer with its own note, in chats too. A Starred list on the map, each pin with "Go to this message". Search finds your notes.
✓Cowork tasks by their own titles. Every task listed under its own name, newest first, not hidden under a folder. The files each task made or was given are kept too, readable after Claude drops the task.
✓Chats, easier to keep. Your chats by month, and Chats as the start screen if you like. A new Claude export in your Downloads folder is offered with one press (it looks only at the list of files inside the .zip; its own checkbox), and when yours gets old, one button opens Claude's export page.
✓A health check. Green, amber or red at the top of the map: is everything still being kept, and what vanished from Claude's sidebar (the copy here stays).
✓An activity log. Every change it made outside its own folder, newest first, and a copy of Claude's settings file before each edit.
✓Search that narrows. Inside every conversation, then by Code, Cowork or chats, account, dates, only Claude's answers, or exact words, and straight to the matching message.
✓A second copy. Once a day to another drive, a USB drive or your OneDrive folder. Nothing is ever deleted there. If the drive isn't plugged in, it tries again at the next update. Plain files, not encrypted, like the folder on your PC. (OneDrive uploads that folder to your own Microsoft account: your choice.)
✓Every computer you own. On the map, pick a folder OneDrive, Google Drive or Dropbox keeps the same on all of them, the same one on each, and every computer shows and searches the others' conversations. Each computer writes only its own subfolder, so they never write over each other.
✓Runs that start by themselves, named and folded. When a timer or a script starts Claude again and again with the same opening, each run gets a plain name from the jobs it worked, and a day's runs fold into one line on the Timeline, so the conversations you held stand out.
✓What each job cost. The Usage page counts those runs per job and per area, this week, last week and the last 8 weeks: "which jobs used the most?" is one look.
✓Plain titles. A conversation whose title says nothing (empty, a made-up name, "Handoff continuation") shows a plain one from what you first asked. Search still finds the old title.
✓More than one Claude folder. If you run Claude Code with a separate folder per account, list those folders in its settings and their Code sessions are kept and searched too, labelled by account.
✓Always current. "Updated 5 min ago" at the top, and an Update now button. When your computer is short of memory it still brings your copies and the list up to date at once, and finishes the heavy parts when memory frees up.
✓Real rules and real decisions. The Rules page leaves out "never mind" and "go with A"; a Not a rule button takes one off for good. Each answer in Decisions shows the question it answered and what happened next.
✓Tells you when a new version is out. A note on the map with a link to what's new. It never downloads or installs anything by itself, and you can switch the check off.
✓A reader that needs no account. Opens, maps and searches your whole history with no login and no plan.
✓A year of keeping up as the app changes under it.

What it would cost you.

Getting back to a working place without a recorddays

If you don't have that personhard to find

An evening proving to yourself that nothing was deletedhours

A product you finished, filed three folders deep, and forgotits launch

The session where it clicked, gone with a login you no longer havehard to get back

Three weeks of decisions with nothing that says why you made themthe rework

The afternoon you were in the right state, and can't be again on purposenot on demand

Even the best case only gets you back to where you were. The files are usually still on your disk. The state you were in when you made them is not on demand. That is what the record insures.

Made for you if

✓you build real things with Cowork or Code in the Claude desktop app, or Claude Code, on Windows
✓you have more than one account, or more than a handful of projects
✓you want to open your computer and carry on, not dig for where you were
✓you have seen an empty sidebar once and do not intend to see it again

Why it exists

Built after a very bad evening.

A bank flagged a card. The subscription lapsed for a day. When the app came back it was signed into the second account, the sidebar was empty, and it took the whole evening to prove that three weeks of work was not deleted. It wasn't. It was on the disk the whole time, with nothing anywhere that said so. Then the first record it wrote found something else: a finished product, ready to launch, three folders deep, that I had forgotten I built. That is the difference between a subscription and a record.

Joshua, who builds it and runs it on his own machine every day

30-day guarantee

The risk is entirely ours.

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.

The price

$149 / year

About $12 a month, for a record of everything the subscription ever produced.

One person, every computer you own.
Renews yearly. Cancel any time: the record and the reader keep working, you just stop getting updates as the app changes.
30 days, every dollar back, one email.

Not on sale yet $149 / year

Questions

Before you buy.

Why does it cost $149 a year?

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 can cost $100 to $200 a month. The best-case recovery without a record is days of skilled work, which at any hourly rate is more than this costs for years. $149 a year is about $12 a month, 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.

What happens if I stop paying?

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.

Is there anything else like it?

As far as we found (October 2026), it is the only tool that keeps a copy of what the Claude desktop app saves on Windows, across all your accounts, with nothing leaving your PC unless you ask it to. Free scripts fix parts of it, mostly from a terminal and often Mac-only; paid tools save claude.ai chats into their own cloud. ConversationKeep does the whole job, Cowork and Code, every account, installed in a minute.

Doesn't the app already have search?

For the account you're signed into, yes, and it's good. ConversationKeep searches what that box can't reach: every account at once, sessions the app no longer lists, the chats you added, and a day when you have no working app at all.

Does it send my conversations anywhere?

Not by itself. It reads local files and writes local files, in its own folder. There is no account and no tracking. Once a day, if you leave its box ticked, it asks conversationkeep.com for one small public file with the newest version number, so it can tell you when a new version is out; nothing about you or your conversations is added to that request. Three exceptions, each your choice: if you pick a OneDrive, Google Drive or Dropbox folder for the second copy or for several computers, that sync program uploads it to your own account there. Ask my history, off until you switch it on: when you press Ask, your question and the few short pieces of your sessions it found on this computer (up to 8) go to Claude through the Claude program signed in on your computer, under your own account, so Claude can write the answer; never a whole conversation, and each question is listed in the Activity log. Read it on my phone, off until you turn it on: the pages go from this computer to your phone over your own home Wi-Fi, after your passcode, never through the internet. Its small search helper (ck.exe) answers your own computer only (and, with the phone switch on, your phone at home, for reading only). The one thing Claude sees is the status line it adds at the start of each new Code session (what it says is under "What does the installer change?"). It also makes small pictures of web pages in your project folders by opening them invisibly in Chrome or Edge; if such a page loads a picture or font from the internet, the browser fetches it, as it would if you opened the page yourself. The "Open Claude's export page" button opens claude.ai in your own browser, like a link, only when you press it; nothing is sent with it.

My Claude plan lapsed. What can I still read?

Everything it kept: every Cowork task and Code session it copied, word for word, from every account, and every chat from the exports you added, with search. Open ConversationKeep from its shortcut and press Read. You need Claude again only to continue a conversation.

What about pages I published on claude.ai?

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 Code 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.

Does it keep my ordinary chats?

Yes, when you add Claude's own export, and only up to that export. Chats in the Chat tab of the desktop app, on claude.ai in a browser and in the phone app are stored by Anthropic online and never saved on your computer, so ConversationKeep can't copy them by itself. To add them: in Claude, open Settings → Privacy → Export data; Claude emails you a download link (it works for about a day); download the .zip; in ConversationKeep open Chats, press Add my chats and pick it. Every chat in it is kept on your computer, searchable and readable with no login, labelled by account. Nothing is sent anywhere. To keep newer chats, add a newer export; adding again never doubles a chat and never removes one. What it keeps by itself, as you work, is Cowork and Code in the desktop app, and Claude Code in a terminal, because those write transcripts to your disk.

What does the installer change?

The installer window lists every change before you click Install. Things you can untick: (1) two entries in Claude Code's settings so your copy updates when a Code session starts or ends; these also add a short status line at the start of each new Code session, which Claude reads, so it goes to Claude with that conversation. It says: which Claude account the app is on (your email), how many sessions and project folders you have, how many belong to another account and its email, your four most recent project folder names, where the map's text file is, and this session's title, folder, start date and tool names. The status line has its own box: untick it and there is no line, and your copy still updates. Later, on the map, choose Full, Short (no email addresses, folder names or titles) or Off. (2) A copy of every transcript in its folder, and on its own box, a copy of the files each Cowork task made or was given (up to 200 MB each). (3) A look in your Downloads folder for a new Claude export at each update: only the .zip files that changed in the last 30 days, and only the list of files inside; it never moves or changes them. (4) Claude Code's 30-day cleanup raised to 10 years. (5) A small Claude skill. (6) Shortcuts on the Desktop and in the Start Menu. (7) With two accounts, if you tick it: copies of sidebar entries between them. The hourly update, if you leave it ticked: one Windows scheduled task, "ConversationKeep update", for your user only, low priority, no window. Always added: its folder, an Installed-apps entry, and the search helper ck.exe, which answers your own computer only and does not start with Windows. Uninstall from Installed apps undoes every one of these. Never at install, only when you press them later: Put it back (one kept Code session back into Claude's folder), Add it on the Rules page (one line in that project's CLAUDE.md; it shows you the line first and keeps the old file), and Read it on my phone (the first time, Windows asks once whether it may use your home network; tick Private networks only). Note: once the 10-year setting is put back, Claude Code goes back to deleting its own Code sessions after 30 days; your copies in the ConversationKeep folder stay.

I mostly use Cowork. Does it keep up by itself?

Yes. Cowork never runs Claude Code's session entries, so ConversationKeep also updates by itself once an hour and a few minutes after you sign in to Windows: a small scheduled task for your Windows user only, at low priority, with no window. It is a checkbox at install; if you untick it, open ConversationKeep now and then and it catches up. Uninstall removes the task.

What does uninstall leave behind?

Only the ConversationKeep folder, with the program and your conversation copies, so nothing is lost by accident. To delete it too: close the ConversationKeep window, press Windows key + R, type %LOCALAPPDATA%, press Enter, and delete the folder named ConversationKeep.

How much disk space does it take?

The program is about 35 MB. The copies take about as much space as Claude's own transcripts: for most people tens to hundreds of megabytes, for someone who uses Claude Code every day a gigabyte or two.

Windows says it "protected my PC".

The installer isn't code-signed yet, so Windows shows that screen for any new program. Click More info, then Run anyway.

Two accounts?

Yes. It shows which account each session was born on, warns when the app is on a different one, and can mirror every Code 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.

Mac?

Not yet. The code is written for it but untested. Email hello@conversationkeep.com and you'll hear the day it ships.

Refunds?

30 days, every dollar, one email. You don't have to explain.

Can I check what it does on my computer?

Yes. What it reads: Claude's own folders (%APPDATA%\Claude\claude-code-sessions, %APPDATA%\Claude\local-agent-mode-sessions and %USERPROFILE%\.claude, plus any other Claude Code folder you list in its settings), and your project folders: the folders directly inside C:\Users\<you>, except standard ones like Documents, Desktop, Downloads, Pictures and OneDrive. And, only when you pick it with Add my chats, the export file Claude emailed you. To spot a new export, it also looks at the .zip files in your Downloads folder that changed in the last 30 days, and in each only at the list of files inside (and the account's email in users.json); it never moves or changes them, and adds nothing without your press (its own checkbox at install).

What it writes and runs: its own folder, %LOCALAPPDATA%\ConversationKeep; two entries and one setting in Claude Code's settings file; a small skill folder; two shortcuts; an Installed-apps entry; the hourly update (one Windows scheduled task for your user, if you leave it ticked); and its search helper ck.exe, which runs in the background but does not start with Windows (it starts with a Code session or when you open ConversationKeep; the hourly update never starts it). With the two-account option on, copies of sidebar entries between your accounts. Uninstall takes back every one of those and leaves only its folder with your copies. Only when you press them: Put it back and Add it on the Rules page, both listed in the Activity log.

Five things you can look at after installing:

The settings file. Press Windows key + R, type notepad %USERPROFILE%\.claude\settings.json, press Enter. You'll see two entries that mention ck.exe and the line "cleanupPeriodDays": 3650 (if you left those two checkboxes ticked).
The folder. Press Windows key + R, type %LOCALAPPDATA%\ConversationKeep, press Enter. Everything it keeps is there as plain files; the conversation copies are in history\transcripts, and the chats you added from Claude's export are in chats.
The network. Press Start, type resmon, open the Network tab and tick ck.exe (ConversationKeep's background helper, in that folder). Every connection it has is to 127.0.0.1, which is your own computer (and, only while Read it on my phone is on, to your phone on your home network).
The app list. Settings → Apps → Installed apps shows ConversationKeep, with its Uninstall button.
The hourly update. Press Start, type Task Scheduler, open it, click Task Scheduler Library: "ConversationKeep update" is there (if you left its checkbox ticked), with its times.

What is the work worth?

Not the $200 a month. Days of skilled work just to get back to where you were, if you have someone. 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 record.

Not on sale yet $149 / year

Windows · installs in about a minute · 30-day refund

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.