Local-first memory layer for OpenClaw, Codex App, and Codex CLI: capture, recall, dedupe, and native sync.
# Add to your Claude Code skills
git clone https://github.com/legendaryvibecoder/gigabrainLast scanned: 5/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-30T15:36:44.670Z",
"npmAuditRan": true,
"pipAuditRan": true
}No comments yet. Be the first to share your thoughts!
30 days in the Featured rail · terms & refunds
Gigabrain is the local-first memory governance & trust control plane for people who run more than one AI agent. When you use Codex, Claude Code, Cursor/Windsurf, OpenClaw, and Hermes against the same work, each one quietly remembers different — and sometimes contradictory — things. Gigabrain gives you one inspectable place to see what they all remember, where each memory came from, what's stale, contradictory, or secret-leaking, and what is safe to hand to the next agent.
The product face is the Memory Passport: an audit report + safe handoff briefs. Underneath it is an event-sourced memory engine — SQLite-backed hybrid recall, deterministic dedupe/audit flows, read-only host-memory adapters, native markdown sync, a claim-slot world model with contradiction detection, and an optional web console.
Gigabrain does not replace native memories and does not claim to be a portable "carry your brain anywhere" bundle. It sits above native memory: it connects, checks, deduplicates, attributes, and audits the memory your agents already keep where the host exposes local files or you provide an explicit export, then writes safe briefs for the next host. Closed cloud memories (ChatGPT, Claude.ai, Gemini, Microsoft Copilot) are manual import/export only — no scraping, no hidden sync. Encrypted, signed, fully round-trippable export bundles are on the roadmap, not shipped today; see the destination audit.
| Host surface | Install | What Gigabrain owns |
|---|---|---|
| OpenClaw | openclaw plugins install |
Registry, native sync, recall orchestration, audit/nightly, memory-slot provider |
| Codex App / CLI | npm install + setup |
Shared project/user memory store, MCP tools, checkpoints, maintenance |
| Claude Code | npm install + setup |
Shared project/user memory store, MCP tools, managed .mcp.json wiring |
| Claude Desktop | claude:desktop:bundle |
Same MCP-backed memory store and tools as Claude Code |
| Hermes Agent | gigabrain-hermes-setup |
MCP tools plus read-only sync for Hermes built-in memory files |
| Local host memories | gigabrainctl sync-hosts |
Read-only local adapters for Codex memories, Claude Code memory, Hermes memory files, Cursor/Windsurf rules, plus explicit manual imports |
| Memory Passport | gigabrainctl passport |
Static Markdown/HTML audit report, readiness verdict, and safe AGENTS.md, CLAUDE.md, ChatGPT, Claude.ai, Gemini, and Copilot handoff briefs |
npm install @legendaryvibecoder/gigabrain
npx gigabrain-codex-setup --project-root /path/to/repo
npx gigabrain-claude-setup --project-root /path/to/repo
npx gigabrain-hermes-setup --config ~/.gigabrain/config.json --workspace-root /path/to/repo
npx gigabrainctl sync-hosts --config ~/.gigabrain/config.json --host codex,claude_code,hermes,cursor,windsurf
npx gigabrainctl passport --config ~/.gigabrain/config.json --output-dir ./gigabrain-passport
This gives Codex, Claude, and Hermes the same local project/user memory store, indexes visible local host memories read-only, then writes a static Memory Passport report plus handoff briefs under ./gigabrain-passport/. See the Memory Passport guide, Codex setup, Claude setup, Hermes setup, the Nimbus Memory Bridge Contract, the destination audit, and the cross-memory pivot.
Manual cloud imports must be explicit:
npx gigabrainctl sync-hosts --config ~/.gigabrain/config.json \
--manual-import ./chatgpt-memory-export.md \
--manual-source-host chatgpt_manual
npx gigabrainctl passport --config ~/.gigabrain/config.json --output-dir ./gigabrain-passport
npm install @legendaryvibecoder/gigabrain
npx gigabrain-codex-setup --project-root /path/to/repo
.codex/actions/verify-gigabrain.sh
npm install @legendaryvibecoder/gigabrain
npx gigabrain-claude-setup --project-root /path/to/repo
.claude/actions/verify-gigabrain.sh
For OpenClaw:
openclaw plugins install @legendaryvibecoder/gigabrain
cd ~/.openclaw/extensions/gigabrain && npm run setup -- --workspace /path/to/workspace
npx gigabrainctl doctor --config ~/.openclaw/openclaw.json
npm install @legendaryvibecoder/gigabrain
npx gigabrain-hermes-setup --config ~/.gigabrain/config.json --workspace-root /path/to/workspace --install --test
hermes gateway restart
Import a legacy Nimbus/OpenClaw backup with provenance:
npx gigabrainctl import-openclaw \
--config ~/.gigabrain/config.json \
--registry /path/to/backup/clawd/memory/registry.sqlite \
--source-label nimbus-backup \
--dry-run
Full guide: Hermes setup Nimbus runtime policy: Nimbus Memory Bridge Contract
Upgrading? See the upgrade guide.
Conversation (OpenClaw / Codex / Claude Code / Claude Desktop)
│
▼
┌──────────────────────────────────┐
│ Gigabrain │
│ (memory layer + MCP server) │
├──────────────────────────────────┤
│ Capture ─► Policy ─► Registry │
│ Recall ◄─ Orchestrator │
│ Host Sync ◄─ Codex/Claude/etc. │
│ Native Sync ◄─► MEMORY.md │
│ World Model (entities/beliefs) │
└──────────────┬───────────────────┘
│
SQLite + FTS5
gigabrain_recall, gigabrain_remember, gigabrain_checkpoint, gigabrain_provenance, gigabrain_recent, gigabrain_sources, gigabrain_sync_status, gigabrain_export_brief, gigabrain_doctor, gigabrain_entity, gigabrain_contradictions, gigabrain_relationshipsMEMORY.md and daily notes alongside the registry for unified recall| Subsystem | Description | Docs |
|---|---|---|
| Memory Passport | Static local audit report and handoff briefs | docs/memory-passport.md |
| Destination audit | Host-by-host integration status and gaps | docs/audits/destination-audit-2026-05.md |
| Launch kit | Positioning, pilot offer, X posts, and static marketing site | docs/launch/gtm-brief.md |
| Sharing model | Multi-host sharing modes and scope rules | docs/sharing.md |
| Cross-memory pivot | Why Gigabrain still matters when native memories exist | docs/cross-memory-pivot-2026-04.md |
| Configuration | Full config reference (runtime, capture, recall, dedupe, LLM, quality) | docs/configuration.md |
| Memory protocol | Capture tags, agent instructions, AGENTS.md | docs/memory-protocol.md |
| Recall pipeline | 11-step orchestrated recall with strategy selection | docs/recall.md |
| Nightly maintenance | Pipeline steps, artifacts, sch |