DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find past decisions and bug fixes before you repeat them with Claude Mem

Use the mem-search tools to look up earlier bugfixes and decisions, then fetch only the relevant details.

Who it is forA developer or agent who must recall why something was built a certain way or how a bug was fixed weeks earlier in the same project.

The problemSearching raw session history is slow, and loading full transcripts costs a lot of tokens.

The outcomeThe agent finds the matching observations by ID, reviews a timeline around them, and loads full details only for the IDs it needs.

What you need first

  • Node.js 20.0.0 or higher
  • Claude Code with plugin support, or a supported agent host such as OpenCode or T3 Code
  • A claude-mem sign-in or your own memory provider key, if you do not use the installer's local option
  • Bun and uv, which the README says are auto-installed if missing

Steps

  1. Confirm the Claude Mem plugin is installed and that Claude Code was restarted
  2. Ask Claude a natural language question about past work in the project
  3. Call search with a query and an optional type filter, for example search(query="authentication bug", type="bugfix", limit=10)
  4. Call timeline on an interesting result to see what happened around it
  5. Call get_observations with the chosen IDs in one batch, for example get_observations(ids=[123, 456])

Prompt for your agent

Using the claude-mem MCP tools, search memory for <topic> in the project at <project path>, then use timeline on the most relevant result and get_observations with the chosen IDs in one batch. Report a short list of decisions or fixes with their IDs. Verify that every ID you report came from the search results.

Caveat. The README describes token savings of about 10x from filtering before fetching, but the exact savings depend on your own results and are not guaranteed.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page