mem-search

Search and retrieve indexed information from a persistent cross-session memory database for development projects.

1|Updated Mar 12, 2026

Search Tags:#development #context #search #retrieval #memory #history

Ready to run

npx skills add https://github.com/LautaroSanz/opencode-mem --skill mem-search-lautarosanz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mem-search
Source: https://github.com/LautaroSanz/opencode-mem/tree/main/.opencode/skills/mem-search
Command: npx skills add https://github.com/LautaroSanz/opencode-mem --skill mem-search-lautarosanz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows you to search and retrieve information from past development sessions, helping you recall previous solutions, decisions, and work done on projects.

Core Features & Use Cases

Cross-Session Memory Search: Query a persistent database of past work.
Chronological Context Retrieval: Understand the timeline around specific observations.
Detailed Observation Fetching: Retrieve full details of past work items.
Manual Saving: Manually save important discoveries, bugs, or decisions to memory.
Use Case: When a user asks "Did we already fix this bug?" or "How did we solve X last time?", this skill can search the memory to provide relevant past solutions.

Quick Start

Search memory for past work related to authentication.

Frequently Asked Questions about mem-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I search past development sessions to recall previous solutions?▼

You can search past development sessions by querying a persistent cross-session memory database. This retrieves past work items, solutions, and decisions using indexed search, allowing you to recall how previous issues were resolved.

What is chronological context retrieval for development memory?▼

Chronological context retrieval is a mechanism that fetches the timeline of observations around specific past work. It helps developers understand the sequence of decisions and actions taken during previous development sessions.

Can I manually save critical bugs and decisions to a development memory database?▼

Yes, you can manually save important discoveries, bugs, and decisions to the persistent memory database. This ensures critical work items are indexed for future search and detailed observation fetching across sessions.

How do I retrieve full details of a past work item from memory?▼

You retrieve full details of past work items by using detailed observation fetching tools. These tools query the persistent memory database to extract comprehensive records of previously saved development work and decisions.

Does cross-session memory search work without external dependencies?▼

Yes, cross-session memory search operates without external dependencies. It relies on an internal persistent database and references to index, search, and retrieve past development work and chronological context.

What's the best way to find out if we already fixed a specific bug in a past session?▼

The best way to check if a bug was fixed is to use indexed search across the persistent memory database. Querying the development history retrieves relevant past solutions and observations related to that specific issue.