Find an earlier Claude Code decision without reading every chat

You remember choosing a way to handle sign-in last week, but the reason is buried in a Claude Code chat. Searching for the project name brings back too much. A detail from the actual decision is often a better starting point.

Search for the reason, not just the project

Open ChatVault and use the chat search to look for a phrase you would have used while weighing the options. A rejected library, an error message, or a route name can narrow the search more than a broad word such as authentication.

1. Start with one rare term from the discussion. If you remember a table or file name, use that first.
2. Open a likely conversation and read the messages around the match. Look for the constraints that led to the choice, including anything you decided not to do.
3. Use Find in the open chat to jump between related words. Keep the decision and its reason together when you export a note.

Check whether the reason still holds

A useful old decision can still be out of date. Compare it with the current branch, dependencies, and requirements. Save a short note with the reason you kept or changed the approach. The chat gives you the history; your current code tells you what is true now.

ChatVault is Free & Opensource for Windows 10 and 11, 64-bit. It reads local coding conversations from supported tools. The source files must still be present on your computer. Reading an old chat helps you find context; check the result against your current code before using it.

See ChatVault on GitHub or download the Windows app.