01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Codex CLI Memory across · shared project memory
Codex CLI Memory across England
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.
Mixed teams shouldn’t fragment knowledge by tool. With MemHub behind it, Codex CLI reads the same project memory as Claude Code and Cursor — one source of truth regardless of which agent is open.
Create your shared memory
Free Community tier. Self-hosted or hosted. No external embedding API required.
acme/codex-cli-memory
synchronizedcontext/main
memories 41
pinned 6
contributors 9
BRIEFING FOR NEW SESSION
What changed since your last pull
02
pattern
Repository layer owns every database transaction
Source: pull request #214
03
bugfix
Refresh tokens rotate atomically under load
Source: auth/session.ts
Claude Code
Cursor
Windsurf
LOCAL FIT
Why England engineering teams choose MemHub
Across England, software teams ship faster when their tools share one memory instead of three silos. Mixed toolchains stop fragmenting knowledge across vendor-specific stores.
Every entry carries authorship and version history, which keeps both humans and auditors comfortable.
- England: connect Claude Code, Cursor, Windsurf, Cline, Codex CLI, or Antigravity to one shared memory. It also plugs into any CLI that speaks MCP or reads a JSON config.
- Data residency you control — run MemHub on infrastructure inside England or let us host it.
- One command onboards the whole team: memhub login, then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI, or any JSON client.
UNIVERSAL COMPATIBILITY
Plugs into any CLI or development tool you use.
If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires the majors; everything else joins as a generic client.
- Claude Code
- Cursor
- Windsurf
- Cline
- Codex CLI (GPT)
- GitHub Copilot
- Google Antigravity
- Gemini CLI
- Aider
- OpenCode
- CI bots via REST
WHAT YOU GET
Codex CLI Memory across England, without the trade-offs.
01
Team-shared
Insights captured by one engineer become available to every teammate’s agent automatically.
02
Offline resilience
The local SQLite outbox queues writes during disconnection and flushes them safely later.
03
Provenance and versions
Every entry records who wrote it and when — trust but verify before an agent acts on it.
04
One command
`memhub connect --ide codex` wires the configuration; `mh login` authorizes it securely.
05
Session-to-session recall
Incremental briefings mean each Codex invocation inherits everything learned since the last pull.
06
Machine-independent
Memory follows the developer across laptops and containers, not just the current working directory.
The honest comparison.
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 |
Connect the tools already in your repository.
One command injects configuration for Claude Code, Cursor, Codex CLI, Google Antigravity, Windsurf, Cline, or any JSON MCP client.
repository terminal
$ npm install --global @simplexlat/memhub
$ memhub login
✓ project resolved · context ready · memory synchronized
Questions, answered straight.
Does Codex CLI support MCP memory?
Yes. Codex CLI consumes MCP servers, and MemHub’s proxy exposes memory, search, and sync status over stdio with no extra daemons.
Where does my data live?
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.
What happens when our connection drops?
Nothing interrupts the work. Writes commit to the local SQLite outbox and synchronize automatically when the shared service is reachable again.
Can we try it without sending data anywhere?
Yes — the local engine works fully offline, and the self-hosted stack keeps even the shared layer on your own PostgreSQL.
How much does it cost?
A Community tier is free, and the Team plan adds multi-project contexts, seats, and higher synchronization limits. Self-hosting is unlimited.
MORE LOCATIONS
Codex CLI Memory in LondonCodex CLI Memory in ManchesterCodex CLI Memory in EdinburghCodex CLI Memory across the United StatesCodex CLI Memory across CanadaCodex CLI Memory across the United KingdomCodex CLI Memory across IrelandCodex CLI Memory across GermanyCodex CLI Memory across FranceCodex CLI Memory across SpainCodex CLI Memory across PortugalCodex CLI Memory across Italy
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