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!
Report
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?
@curiouskitty the main reason was the need to sync between devices - need that I have + the team plan in which I really believe collaboration will improve if you can see what your colleague did to fix that bug. Same for skill sharing and mcp tool sharing - I've used postgres for a better scaling really but for a single dev sqlite could have worked as well. Please let me know if you've tried it and if you have any feedback!
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.
chat-recall
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!
This is going to save me a lot of time when I try to look for chats about certain topics. Good luck!
chat-recall
@elene_kvitsiani yes that was the goal indeed! I hope it's useful! Let me know if you have any feedback!
Great work! I needed this because I don't remember anything
chat-recall
@rekhviashvili haha! same here. Please let me know if you have any feedback!
Product Hunt
chat-recall
@curiouskitty the main reason was the need to sync between devices - need that I have + the team plan in which I really believe collaboration will improve if you can see what your colleague did to fix that bug. Same for skill sharing and mcp tool sharing - I've used postgres for a better scaling really but for a single dev sqlite could have worked as well.
Please let me know if you've tried it and if you have any feedback!
Paste
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.