
Mem Search
This is how you search across past Claude sessions without burning tokens on irrelevant details. The workflow is smart: search returns a lightweight index with IDs and titles, timeline shows you what happened before and after interesting moments, then you only fetch full details for the observations that matter. That three-step filter saves roughly 10x on tokens compared to fetching everything upfront. Use it when someone asks "didn't we already fix this?" or "how did we handle authentication last time?" The batch fetch with get_observations is a nice touch. If you want synthesized answers instead of raw records, there's a knowledge agent mode that reads your history and responds conversationally.
- install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.
- 8
- skills.sh installs
- 9.3K
- GitHub stars
- 115.5K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add thedotmack/claude-mem --skill mem-search --agent claude-codeInstalls into .claude/skills of the current project.
Files
mem-search
Layered workflow. Do not dump full observations until IDs are filtered, and do not reach for raw tool bodies until the summaries came up short.
search(query)— index with IDstimeline(anchor=ID)— nearby contextget_observations(ids=[...])— full details for those IDs onlyget_tool_uses(ids=[...])— the ORIGINALtool_input/tool_responsefor specific tool calls. Last resort: these are unsummarized and can run to thousands of tokens each.
Stamp platformSource as cursor or grok-bot on writes for this host. When reading, do not drop the other host unless asked.
If MCP is missing, run the install skill first (npx claude-mem install --ide <host>).
Sponsors
Details
- Repository
- github.com/thedotmack/claude-mem
- Categories
- Backend & APIs, Databases
- First seen
- Apr 16, 2026