What problem does it solve? Managing a gbrain knowledge base involves recurring operational tasks — syncing git repos into the brain, running multi-hour imports, monitoring embedding health, and recovering from PGLite WASM crashes — that fail silently or time out without the right procedures. ## Core Features & Use Cases - Read-Enrich-Write Loop: Standardized pattern for searching, updating, and writing brain pages via MCP tools like mcp_gbrain_search and mcp_gbrain_put_page. - Sync & Large Imports: Incremental and full git-to-brain sync, plus background execution patterns for 2+ hour imports of 11,000+ files with progress monitoring. - Health & Diagnostics: Health dashboards, orphan/stale page detection, embed coverage checks, and ingest logging after significant operations. - PGLite Crash Recovery: Step-by-step diagnosis of WASM runtime failures after WSL2 kernel upgrades, with migration guidance to native PostgreSQL. - Use Case: After a WSL2 kernel upgrade breaks all gbrain cron jobs with PGLite WASM abort errors, follow the in-memory vs file-backed diagnostic tests to confirm data directory corruption, then migrate to native PostgreSQL and re-sync from the brain repo. ## Quick Start Ask the agent to run a brain health check and sync the local brain repo using the gbrain MCP tools.