Building a Persistent AI Knowledge Infrastructure with OpenClaw

A developer has built a full knowledge infrastructure system called 'Brain' on top of OpenClaw to address the statelessness problem common in AI setups. The system provides persistent memory across sessions, allowing users to query past decisions and workflow history.
Core Architecture
Brain serves as the central knowledge service where documents are ingested, chunked, and embedded locally using Ollama. Data is stored across multiple databases: Postgres, MongoDB, and Qdrant, with relationships mapped in a Memgraph graph database. This makes every decision, session, and workflow run searchable and connected.
Search and Retrieval
Search in Brain uses hybrid retrieval combining semantic search via Qdrant with BM25 full-text search from Postgres, merged using reciprocal rank fusion. Results are automatically deduplicated and context-budgeted before synthesis.
RAG Agent and Plugin System
On top of Brain sits a RAG Agent that runs a complete pipeline: retrieve → graph expand → fuse → synthesize, all powered by local Ollama models. The agent estimates confidence on every answer and automatically logs 'knowledge gaps' to a pending queue when confidence is low.
The system includes a clean plugin system with 33+ typed tools that agents can call, including: brain_search, brain_ingest, brain_rag_query, brain_graph_slice, and brain_condense_domain. Every operation has a strict, well-typed interface.
Workflows and Observability
Workflows are first-class citizens in this system. Multi-step pipelines—orient, fetch, inspect, synthesize, log—can be run either through agents or via a deterministic runner on a cron schedule with zero LLM involvement. Telemetry and observability remain consistent either way.
Each agent has a strict mandate and communicates through structured handoffs, with all activity tracked back into Brain as searchable history. A Python drift checker compares live agent configs against Brain snapshots, automatically logging structured events when tool allowlists or plugin versions change.
Local Deployment and Future Plans
The entire system runs locally using Ollama for embeddings and synthesis, with Docker for all the stores. There are no OpenAI calls or external APIs for the core intelligence layer.
Next steps include migrating the RAG agent to LlamaIndex Workflows, building out a shared brain-client SDK, and tightening the API surface. RAG endpoints are moving to a /v1/rag/ prefix, realm is becoming a header, and leaky DB facades are getting properly abstracted.
📖 Read the full source: r/openclaw
👀 See Also

CostClaw: Free Local Cost Tracking Dashboard for OpenClaw Agents
CostClaw is a free, local plugin that captures every LLM call via OpenClaw's native hooks and provides a dashboard showing model breakdowns, per-session costs, and hourly spend charts. The developer discovered their heartbeat agent was running Claude Sonnet every 3 minutes 24/7, costing $60/month, and switching to Haiku cut their bill by ~65%.

git-courer: An MCP Server That Forces AI Agents to Write Proper Git Commit Messages
git-courer is a local MCP server in Go that intercepts diffs from AI coding agents and translates them into structured, human-readable commit messages with WHY and WHAT sections.

How Mendral Cut LLM Costs by Upgrading to Opus: Triager Pattern, SQL Access, and Sub-Agent Architecture
Mendral switched from Sonnet to Opus 4.6 for CI failure analysis but reduced costs by using a Haiku triager to divert 80% of failures, giving agents SQL access to ClickHouse instead of pushing logs, and spawning cheap sub-agents to do the actual digging.

Anthropic Launches Claude for Small Business with Pre-Built Workflows for QuickBooks, HubSpot, Canva
Claude for Small Business is a toggle-install package within Claude Cowork that connects to QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace, and Microsoft 365, with 15 ready-to-run agentic workflows for payroll, month-end close, invoicing, campaign management, and more.