Your team has done months of work with AI assistants. Claude Code, Codex, Cursor and OpenCode each keep a full record of it, in its own format, and none can read the others. One command reads what they wrote and turns it into one searchable history. Passwords come out before anything leaves your computer. Your assistant searches it itself, so it stops asking what you decided last month. It also finds keys that leaked into old chats, and checks which still work.
Ctrl+F doesn't work on your brain. That was the whole problem I had.
I run four assistants — Claude Code, Codex, Cursor and OpenCode — depending on the job. Each one keeps a complete record of everything it did. Each one is blind to the other three. So I kept re-explaining the same architecture, and twice I watched one rebuild something another had finished the week before.
chat-recall reads what they already wrote and turns it into one searchable history. One command.
The part I did not plan for is the leaked keys. Old chats are full of pasted credentials, and it now tells you which ones still work. A dead key is cleanup. A live one is an incident.
Three things it does that I use every day:
- A new laptop already knows everything. Sign in and the whole history is there. - Try a new assistant without starting over. Every add-on follows you across. - Bugs turn into tasks on their own, with the fix already sketched out.
- Scan for passwords/secrets before sending any data.
Free forever for one person, on your own hardware. $10 a month if we host it. The whole repo is source-available under Elastic License 2.0.
Which assistant would you want indexed that I'm missing? I am happy to add more!
Does it pick up both Claude and ChatGPT history, or only the chats it sees in the browser?
looks really cool and really OCD-friendly so i am gonna definitely subscribe. I have a question though. How does CR handle conflicting or outdated context? Like if Claude, Codex and Cursor reach different conclusions, or an earlier decision is later reversed, how does it determine the current source of truth, preserve provenance and prevent stale assumptions from being passed to the next "guy"?
Came for the search, stayed for the leaked key detection. When it finds a key that still works, does it flag it or actually help you rotate it? Also wondering if it can pull in regular ChatGPT or Claude app chats, or just the coding assistants.
This is going to save me a lot of time when I try to look for chats about certain topics. Good luck!
You’ve chosen a Postgres-centered index (FTS + vectors + KG + findings) and a large MCP tool surface with “narrow-only” safety constraints. What tradeoffs did you make versus a simpler no-server/no-index approach, and which parts of that architecture have proven most important in day-to-day developer workflows?
About chat-recall on Product Hunt
“Ctrl+F for every conversation you've had with an AI”
chat-recall launched on Product Hunt on September 11th, 2026 and earned 95 upvotes and 13 comments, placing #11 on the daily leaderboard. Your team has done months of work with AI assistants. Claude Code, Codex, Cursor and OpenCode each keep a full record of it, in its own format, and none can read the others. One command reads what they wrote and turns it into one searchable history. Passwords come out before anything leaves your computer. Your assistant searches it itself, so it stops asking what you decided last month. It also finds keys that leaked into old chats, and checks which still work.
chat-recall was featured in Developer Tools (519.8k followers), Artificial Intelligence (479.1k followers) and Security (2.9k followers) on Product Hunt. Together, these topics include over 213.2k products, making this a competitive space to launch in.
Who hunted chat-recall?
chat-recall was hunted by darkkraft. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how chat-recall stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
darkkraft
Hey Product Hunt 👋
Ctrl+F doesn't work on your brain. That was the whole problem I had.
I run four assistants — Claude Code, Codex, Cursor and OpenCode — depending on the job. Each one keeps a complete record of everything it did. Each one is blind to the other three. So I kept re-explaining the same architecture, and twice I watched one rebuild something another had finished the week before.
chat-recall reads what they already wrote and turns it into one searchable history. One command.
The part I did not plan for is the leaked keys. Old chats are full of pasted credentials, and it now tells you which ones still work. A dead key is cleanup. A live one is an incident.
Three things it does that I use every day:
- A new laptop already knows everything. Sign in and the whole history is there.
- Try a new assistant without starting over. Every add-on follows you across.
- Bugs turn into tasks on their own, with the fix already sketched out.
- Scan for passwords/secrets before sending any data.
Free forever for one person, on your own hardware. $10 a month if we host it. The whole repo is source-available under Elastic License 2.0.
Which assistant would you want indexed that I'm missing? I am happy to add more!