Standardize on idempotent write endpoints
Source: architecture.md
Codex CLI Memory in · shared project memory
Terminal-native engineers lose hard-won knowledge every time a shell closes. MemHub’s durable outbox and cloud sync give Codex CLI a memory that survives reboots, travels across machines, and reaches the rest of the team.
AGENTS.md describes the repo as it is; MemHub records how it got that way. Connect Codex CLI once and every constraint, workaround, and architectural bet becomes retrievable context forever.
Free Community tier. Self-hosted or hosted. No external embedding API required.
context/main
memories 41
pinned 6
contributors 9
BRIEFING FOR NEW SESSION
Source: architecture.md
Source: pull request #214
Source: auth/session.ts
LOCAL FIT
In San Diego, software teams ship faster when their tools share one memory instead of three silos. Distributed squads stay aligned because every session opens with the same briefing.
MemHub runs hosted or fully self-hosted, so the storage boundary follows your compliance requirements rather than dictating them.
UNIVERSAL COMPATIBILITY
If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires the majors; everything else joins as a generic client.
WHAT YOU GET
The local SQLite outbox queues writes during disconnection and flushes them safely later.
Every entry records who wrote it and when — trust but verify before an agent acts on it.
`memhub connect --ide codex` wires the configuration; `mh login` authorizes it securely.
Incremental briefings mean each Codex invocation inherits everything learned since the last pull.
Memory follows the developer across laptops and containers, not just the current working directory.
Insights captured by one engineer become available to every teammate’s agent automatically.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Status quo | With MemHub |
|---|---|
| Context lives in heads and DMs | Memory is structured, shared, and searchable |
| Every agent re-learns the repo | Sessions open pre-briefed with only what changed |
| Rules files cap out at ~2k tokens | Unbounded versioned history stays one query away |
One command injects configuration for Claude Code, Cursor, Codex CLI, Google Antigravity, Windsurf, Cline, or any JSON MCP client.
$ npm install --global @simplexlat/memhub
$ memhub login
✓ project resolved · context ready · memory synchronized
Locally first — the outbox database sits in ~/.memhub. Cloud copies go to your MemHub organization’s PostgreSQL instance, or to your own hardware if you self-host.
Yes. Codex CLI consumes MCP servers, and MemHub’s proxy exposes memory, search, and sync status over stdio with no extra daemons.
Nothing interrupts the work. Writes commit to the local SQLite outbox and synchronize automatically when the shared service is reachable again.
Yes — the local engine works fully offline, and the self-hosted stack keeps even the shared layer on your own PostgreSQL.
A Community tier is free, and the Team plan adds multi-project contexts, seats, and higher synchronization limits. Self-hosting is unlimited.
MORE LOCATIONS
EXPLORE OTHER USE CASES
AI Agent Memory
Give every AI coding agent a persistent, team-wide memory.
MCP Memory Server
A hosted MCP memory server your whole team connects to in one command.
Claude Code Memory
Claude Code memory that survives sessions and reaches the whole team.
Cursor Memory
Carry Cursor context across sessions, machines, and teammates.
Cross-Agent Memory
One memory behind Claude Code, Cursor, Codex CLI, and Antigravity.
Developer Knowledge Base
A living knowledge base that writes itself while your team codes.
Self-Hosted AI Memory
Run the entire memory stack on your own PostgreSQL — nothing leaves.
Coding Agent Context
Context engineering for coding agents — brief, don’t dump.
Engineering Decision Log
An ADR habit your team will actually keep — logged by the agents doing the work.
Agent Memory Database
A real database behind agent memory — PostgreSQL, pgvector, row-level security.
Windsurf Memory
Persistent Windsurf context shared with every other agent on the team.
Cline Memory
Give Cline a memory that survives tasks, machines, and teammates.
Copilot Team Memory
What Copilot’s custom instructions can’t hold, MemHub remembers.
Antigravity & Gemini Memory
Persistent context for Google Antigravity, Gemini CLI, and the agents around them.
THE NEXT SESSION STARTS HERE