Moerae - AI Memory

Store and retrieve agent memories via embedded vectors and HNSW search.

5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Moerae-AI/Moerae --skill moerae-ai-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Moerae - AI Memory
Source: https://github.com/Moerae-AI/Moerae/tree/main
Command: npx skills add https://github.com/Moerae-AI/Moerae --skill moerae-ai-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moerae - AI Memory reduces the effort of building and maintaining an external, manually indexed memory layer by letting you store content once and retrieve it later through a simple put-and-search workflow, while the system handles embedding, indexing, and lifecycle management.

Core Features & Use Cases

  • Automated local embedding and vector indexing: store data for semantic retrieval without manual indexing or context-window management.
  • Hierarchical scoping with conversation isolation and project-level promotion: search within a conversation by default, and optionally search promoted content across a project.
  • Large-content handling via metadata summaries: automatically switch to embedding metadata only for longer inputs, while still allowing full retrieval later.

Quick Start

Store a memory in a project by asking: “Moerae, put into project myproject the fact 'The API rate limit is 1000 req/min' and make it searchable later.”

Frequently Asked Questions about Moerae - AI Memory

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

FAQPage Schema
How do I store and retrieve semantic memory for AI agents locally?

You can build semantic memory for AI agents by using a put-and-search workflow that turns content into embedded vectors, stores them in SQLite, and retrieves relevant nodes via HNSW vector search. This handles indexing and lifecycle management automatically.

How does semantic memory handle large text ingestion without exceeding token limits?

For large text ingestion, semantic memory systems enforce a max_indexable_tokens threshold and automatically switch to embedding metadata summaries only, while preserving the full content for later retrieval to avoid exceeding token limits.

Do I need a local embedding model to use SQLite for vector search and memory storage?

Yes, you need a local GGUF model to generate embeddings for vector search. The system stores these embedded nodes and segment state locally in SQLite, ensuring data remains isolated without external API dependencies.

How do I scope AI agent memory searches to a specific conversation or promote it across a project?

AI agent memory supports hierarchical scoping by isolating searches within a single conversation by default. You can promote specific memory nodes to search promoted content across the entire project scope.

What is the best way to manage the lifecycle of stored vector nodes in a local SQLite database?

Managing stored vector nodes requires applying segment lifecycle rules to handle promotion and eviction. This ensures your SQLite database maintains relevant semantic memory nodes without manual context-window management or cleanup.