More than a vector database with an agent label
GBrain is an agent-facing knowledge system, not merely a place to store embeddings. Markdown files in a Git repository remain the record, while PGLite or Postgres supplies search, graph edges, timelines, jobs, access controls, and operational state. Agents can capture material, retrieve raw pages, or ask for a synthesized answer with citations and a note about stale, missing, contradictory, or unsupported information.
That final step is the main reason to consider it. Most retrieval tools return passages and leave the calling model to assemble them. gbrain think combines retrieval and synthesis behind one operation. Automatic links turn Markdown references into typed relationships such as employment, attendance, or investment, allowing multi-hop questions that vector similarity handles poorly.
GBrain also includes ingestion, entity and fact extraction, a durable job queue, background enrichment, contradiction checks, health checks, migrations, and a large agent skillpack. Treat it as knowledge infrastructure, not a weekend plugin.
The local path is genuinely approachable
Installation comes from GitHub through Bun, not the unrelated npm package named gbrain. A trial initializes an embedded PGLite database, imports Markdown, and exposes an MCP server over standard input. Claude Code and Codex connect with one command, and the reduced surface presents five memory verbs instead of the full catalog of 110 operations.
PGLite removes Docker and database administration, but it is a one-process system. One running MCP server owns the data directory. A second Claude session, Codex process, or separate CLI health check cannot open the same brain concurrently. Issue 3978 says the error is clear after the collision, while the client setup guides do not warn users beforehand. Stop the server for maintenance or move to Postgres before connecting several processes.
Embeddings are another dependency. Initialization can detect provider keys, ask the user to choose, or defer setup. Local recipes exist, but the quality path still involves choosing, pricing, and monitoring embedding and reranking services. Provider or dimension changes can also require reindexing.
Shared brains demand real operations
The company design uses Postgres, several sources, HTTP MCP, OAuth clients, scopes, and optional slug-prefix restrictions. The author reports fuzz testing across read paths with zero source leaks. The security documentation states the crucial boundary: source scoping protects HTTP MCP, not a raw database connection. Agent containers must not receive the Postgres password or share a network where they can bypass the application.
The company tutorial estimates about 90 additional minutes after the personal setup, then adds source design, client registration, TLS or tunneling, cron jobs, skills, monitoring, and onboarding. It is useful documentation, but this is not a turnkey multi-tenant service. Operators own backups, upgrades, secrets, database capacity, budgets, permissions, and incident response.
The HTTP server has thoughtful defaults: loopback binding, default-deny CORS, rate limits, hashed tokens, audit logs, and dynamic client registration disabled unless enabled. Internet-facing deployments still need careful reverse-proxy configuration and a protected Postgres network.
Retrieval ambition meets retrieval edge cases
Hybrid search combines vector and keyword retrieval, rank fusion, source boosts, graph signals, reranking, title aliases, and result explanations. The project publishes methodology and evaluation commands rather than relying only on a demo. Release 0.44.0.0 added BrainBench, a hermetic memory test suite with a synthetic corpus, isolation checks, continuity tests, and a CI baseline. Its notes distinguish the production OpenClaw seam from Claude Code and Codex contract-level rows.
Current issues show why corpus-specific evaluation matters. Issue 3982 demonstrates that changing the requested result count changes the inner candidate pool, so a page can rank first at a limit of five and vanish at three. A longer-running ranking issue has several independent reproductions. Issue 3986 explains that stock Postgres tokenization does not give space-less CJK prose a useful keyword fallback, leaving those brains dependent on vectors even when search is described as hybrid.
Build a gold query set from your own notes, languages, page sizes, and naming conventions. Run it on every upgrade, inspect search explanations, and do not equate a green generic benchmark with correct retrieval for your organization.
Automation can create cost as well as value
The overnight dream cycle and ingestion pipelines can keep a brain fresh without manual filing. They can also make provider calls while nobody is watching. Issue 3973 reports that enabling image OCR lets routine imports call a paid OCR provider once per image without a durable total call or spending ceiling. Until a bounded path exists, image-heavy operators should disable that feature or enforce external limits.
Some evaluation and remediation commands do include budgets, health diagnostics, and auditable jobs. Still, each integration needs its own cost review. Retries, large imports, multiple workers, OCR, synthesis, and enrichment can all change the bill.
Extremely active, still moving quickly
GBrain was pushed on August 11, 2026, and release 0.44.0.0 arrived one day earlier. Eleven other releases shown by GitHub landed between August 1 and August 10. The repository had 438 open issues and pull requests, with fixes and detailed reports moving throughout August 11. This is exceptional activity, but the version remains below 1.0 and pinning is essential.
Use GBrain when persistent agent memory is important enough to own as a system. Start with one local brain and five memory verbs. Prove capture, retrieval, citations, costs, and recovery on real data. If those pass, move to Postgres and scoped clients deliberately. Only teams willing to operate the whole brain should adopt the whole brain.