home / skills / openclaw / skills / cortex-ai
This skill helps AI agents retain persistent, structured memory across sessions using a git-tracked vault, mind, and hybrid search.
npx playbooks add skill openclaw/skills --skill cortex-aiReview the files below or copy the command above to add this skill to your agents.
---
name: cortex
description: "Persistent memory for AI agents by Sigma Labs. Knowledge graph, hybrid search, entity tracking, and structured recall across sessions. File-based, git-tracked, zero-LLM."
---
# Cortex
Persistent memory for AI agents. Built by [Sigma Labs](https://github.com/sigmalabs-ai).
- **Mind** — Behavioral memory. Decisions, lessons, preferences, and 19 typed entries with decay, reinforcement, and consolidation.
- **Vault** — Document store with CRUD and hybrid search. Every write is a git commit.
- **Observer** — Automatic memory extraction from conversations.
- **Search** — Hybrid (BM25 + semantic + temporal). File-based, git-tracked.
## Links
- GitHub: [sigmalabs-ai/cortex](https://github.com/sigmalabs-ai/cortex)
- Original v1: [waynevaughan/cortex](https://github.com/waynevaughan/cortex) (est. Feb 13, 2026)
- License: MIT
This skill provides persistent memory and structured recall for AI agents, built to capture, search, and manage knowledge across sessions. It combines a typed behavioral memory, a git-backed document vault, automatic extraction from conversations, and a hybrid search engine. The design is file-based and zero-LLM, focusing on auditability and reproducible memory state.
The system records memories in two complementary layers: a Mind module for behavioral, typed entries with decay and reinforcement, and a Vault for document storage where every write becomes a git commit. An Observer watches interactions and extracts salient facts automatically into the memory graph. Search uses a hybrid approach (BM25 + semantic vectors + temporal ranking) to return relevant results that respect entity tracking and time-based decay.
Is a language model required to use this memory system?
No. Storage and indexing are zero-LLM; semantic vectors can be integrated but the system itself is file-based and operates without requiring an LLM.
How are changes to memory tracked?
Every Vault write is a git commit, providing a chronological, auditable history for all document changes.
Can the Observer be customized?
Yes. Extraction rules and thresholds can be tuned to match your domain and to reduce false positives.