This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Lore
Cited recall from local Codex and Claude Code chats
Lore lets a fresh Codex task or Claude Desktop chat find decisions, constraints, and unfinished work in accessible local Codex, Claude Code, and Qwen Code sessions. It returns source references so you can verify the answer. The archive stays on your Windows PC. Free alpha.24; ordinary ChatGPT and Claude cloud chats are outside this release.
I built Lore because I was tired of being the historian for my coding agents. I'd switch from Codex to Claude and spend the next chat reconstructing decisions we'd already made.
The alpha is deliberately narrow. A fresh Codex task or Claude Desktop chat can ask Lore for evidence from accessible local Codex, Claude Code, and Qwen Code sessions. It returns source references, so you can check what actually happened. The archive stays on your Windows PC.
It does not automatically read ordinary ChatGPT or Claude cloud chats. The Windows binary is unsigned, and a clean-PC install is still unverified. This alpha is free and currently closed source.
If you have old local coding sessions on Windows, I'd love a brutal test: ask a fresh agent about a decision absent from the new chat. Did Lore install, answer correctly, and cite the original message? Tell me where it fails.
About Lore on Product Hunt
“Cited recall from local Codex and Claude Code chats”
Lore was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #146 on the daily leaderboard. Lore lets a fresh Codex task or Claude Desktop chat find decisions, constraints, and unfinished work in accessible local Codex, Claude Code, and Qwen Code sessions. It returns source references so you can verify the answer. The archive stays on your Windows PC. Free alpha.24; ordinary ChatGPT and Claude cloud chats are outside this release.
On the analytics side, Lore competes within Productivity, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.7M followers on Product Hunt. The dashboard above tracks how Lore performed against the three products that launched closest to it on the same day.
Who hunted Lore?
Lore was hunted by Faizan Khan. 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.
For a complete overview of Lore including community comment highlights and product details, visit the product overview.
Faizan Khan
I built Lore because I was tired of being the historian for my coding agents. I'd switch from Codex to Claude and spend the next chat reconstructing decisions we'd already made.
The alpha is deliberately narrow. A fresh Codex task or Claude Desktop chat can ask Lore for evidence from accessible local Codex, Claude Code, and Qwen Code sessions. It returns source references, so you can check what actually happened. The archive stays on your Windows PC.
It does not automatically read ordinary ChatGPT or Claude cloud chats. The Windows binary is unsigned, and a clean-PC install is still unverified. This alpha is free and currently closed source.
If you have old local coding sessions on Windows, I'd love a brutal test: ask a fresh agent about a decision absent from the new chat. Did Lore install, answer correctly, and cite the original message? Tell me where it fails.