BrainX V6

Store and retrieve OpenClaw agent memories via PostgreSQL pgvector semantic search.

32|7|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Mdx2025/BrainX-The-First-Brain-for-OpenClaw --skill brainx-v6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: BrainX V6
Source: https://github.com/Mdx2025/BrainX-The-First-Brain-for-OpenClaw/tree/main
Command: npx skills add https://github.com/Mdx2025/BrainX-The-First-Brain-for-OpenClaw --skill brainx-v6

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

OpenClaw agents lack long-term, searchable memory across sessions, so repeated decisions, gotchas, and operational learnings get lost and cannot be reliably recalled later.

Core Features & Use Cases

  • Persistent semantic memory: Stores and retrieves curated memories using PostgreSQL + pgvector embeddings.
  • Retrieval + context injection: Performs semantic search and formats selected memories for prompt injection.
  • Governance and safety-first recall: Uses verification states, sensitivity controls, and conservative rollout of runtime surfaces.
  • Maintenance automation: Supports lifecycle management, deduplication, contradiction handling, diagnostics (doctor), and backup/restore.

Quick Start

Run this to store a new durable memory for a deployment context: brainx add "Use pgvector cosine similarity for semantic recall" --type decision --context project:example --importance 8.

Frequently Asked Questions about BrainX V6

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

FAQPage Schema
How do I add persistent semantic memory to OpenClaw agents for cross-session recall?

Persistent semantic memory is added to OpenClaw agents by capturing, embedding, and storing operational learnings in PostgreSQL with pgvector. This enables cross-session recall and shared knowledge retrieval for ongoing workflows.

Do I need PostgreSQL and OpenAI embeddings to use pgvector for agent memory?

Yes, using pgvector for agent memory requires PostgreSQL with the pgvector extension and OpenAI embeddings to store and retrieve durable vector memories. These dependencies are strictly enforced for semantic search operations.

How do I store a durable decision memory and inject it into an agent prompt later?

You store a durable decision memory using the CLI add command with context and importance flags, then retrieve and inject it via semantic search that formats selected memories for prompt injection during agent runtime.

What is the best way to manage agent memory lifecycle, deduplication, and contradictions?

The best way to manage agent memory lifecycle is using built-in maintenance automation commands for deduplication, contradiction handling, and diagnostics. These tools support ongoing memory health and backup or restore operations.

How does sensitivity control and PII scrubbing work during agent memory recall?

Sensitivity control and PII scrubbing work during recall by enforcing verification states and conservative rollout of runtime surfaces. This governance ensures safe prompt injection and prevents sensitive data from leaking into agent contexts.

Why are my OpenClaw agent operational learnings getting lost across sessions?

OpenClaw agent operational learnings get lost across sessions because the agents lack long-term, searchable memory. Storing these learnings as pgvector embeddings in PostgreSQL solves this by enabling reliable semantic recall later.