
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 consolidates conversation histories from various AI assistants into a single searchable format, enhancing productivity for developers. It ensures security by processing data locally and identifying potential security risks, such as leaked keys.
Scored deterministically. Only candidates that fire a story trigger are sent to a model, so this one has no written angle.
Gaps in our data, not findings about the product. Their weight is redistributed across the 6 we did measure.
A source that found nothing is a measurement. A source that has not run is a gap. Neither means the launch lacks the thing.
Overall, commenters express excitement about the time-saving potential, with some inquiries about specific functionalities.
<p>This is going to save me a lot of time when I try to look for chats about certain topics. Good luck!</p>
<p>Hey Product Hunt 👋<br><br>Ctrl+F doesn't work on your brain. That was the whole problem I had.<br><br>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.<br><br>chat-recall reads what they already wrote and turns it into one searchable history. One command. <br><br>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.<br><br>Three things it does that I use every day:<br><br>- A new laptop already knows everything. Sign in and the whole history is there.<br>- Try a new assistant without starting over. Every add-on follows you across.<br>- Bugs turn into tasks on their own, with the fix already sketched out.</p><p>- Scan for passwords/secrets before sending any data.<br><br>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.<br><br>Which assistant would you want indexed that I'm missing? I am happy to add more!</p>
<p>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 <strong>current</strong> source of truth, preserve provenance and prevent stale assumptions from being passed to the next "guy"?</p>
<p>Great work! I needed this because I don't remember anything</p>