simple-agent-memory

Store and retrieve project-specific knowledge across AI sessions using file-based memory.

Updated May 6, 2026
One-click install
npx skills add https://github.com/lucidfrontier45/my-opencode-settings --skill simple-agent-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simple-agent-memory
Source: https://github.com/lucidfrontier45/my-opencode-settings/tree/main/skills/simple-agent-memory
Command: npx skills add https://github.com/lucidfrontier45/my-opencode-settings --skill simple-agent-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of context loss between conversations by providing a structured, persistent storage system for research findings, architectural decisions, and project-specific knowledge.

Core Features & Use Cases

  • Persistent Knowledge Base: Stores critical information in a local .memories directory that survives across different sessions.
  • Summary-First Retrieval: Uses a standardized frontmatter approach to allow agents to quickly scan and identify relevant information without reading entire files.
  • Use Case: When working on a complex feature, use this skill to save the rationale behind specific architectural choices or to document tricky bugs, ensuring you can recall the exact context when resuming work weeks later.

Quick Start

Ask the agent to remember the current architectural decision regarding the database schema and save it to the project-context category.

Frequently Asked Questions about simple-agent-memory

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

FAQPage Schema
How do I persist project context and architectural decisions across different AI agent sessions?

AI agents retrieve stored project knowledge quickly using a summary-first metadata approach with standardized frontmatter. This allows agents to scan and identify relevant information without reading entire memory files.

How do I save architectural decisions to a searchable knowledge base for later retrieval?

This memory system requires ripgrep for efficient searching and standard file system access for managing memory categories. It relies entirely on local file infrastructure rather than external databases or specialized services.

Why does my AI agent lose previous research findings when starting a new conversation?

AI agents lose context between conversations because they lack persistent storage. Implementing a structured memory system solves this by saving research findings and architectural choices in a local directory that persists across different sessions.

What is the best way to manage work-in-progress status for complex features across multiple AI sessions?

The best way to manage work-in-progress status is using a persistent knowledge base that stores project-specific knowledge locally. This ensures you can recall exact context and tricky bug details when resuming work weeks later.

Does this file-based agent memory system require any external databases to store project knowledge?

This file-based agent memory system does not require external databases, relying solely on standard file system access to manage memory categories. It uses ripgrep to enable efficient searching across the stored local knowledge files.