01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Codex CLI Memory in · shared project memory — local-first · offline-ready
Codex CLI Memory in Singapore
Stop starting Codex CLI with fresh eyes. MemHub gives Codex persistent context — decisions committed this morning brief tonight’s session automatically. Shell closes, memory doesn’t.
Terminal work shouldn’t evaporate when the shell closes. MemHub’s durable outbox + cloud sync gives Codex memory that survives reboots and travels across machines.
Start free — get briefed in 2 min
Free for 1 project · No card · Self-host or we host · No external API
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
WHY IT MATTERS HERE
Why Singapore engineering teams choose MemHub
In Singapore, 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.
- Built for Singapore: regional HQs running distributed engineering across ASEAN.
- Local-first writes keep sessions productive through outages and travel.
- 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 in Singapore, without the trade-offs.
01
One insight, whole team
A fix found on your box is on every teammate’s next Codex session — automatically.
02
Keep working on the plane
SQLite outbox queues writes offline and flushes safely later — no work hostage to VPN.
03
Verify before you act
Every entry has author, source, and version — trust but check before the agent runs.
04
Wired in one line
memhub connect --ide codex + mh login — configured securely in seconds.
05
Shell closes, memory doesn’t
Each Codex invocation inherits what changed since last pull — incremental briefing, not amnesia.
06
Take it to any machine
Memory follows you across laptops/containers — not just the current checkout.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Without MemHub | With MemHub |
|---|---|
| Context lives in heads and DMs → onboarding takes days | Structured, searchable memory → new dev/agent productive in minutes |
| Every agent re-learns the repo from scratch | Sessions open pre-briefed with only what changed — zero re-explaining |
| Rules files cap out at ~2k tokens | Unbounded versioned history stays one query away — never cap again |
| Decisions re-litigated, bugs re-introduced | Pinned invariants prevent regressions — agents respect past calls |
Keep your stack. Add shared memory.
One command for Claude Code, Cursor, Codex, Windsurf, Cline or any MCP client. No new editor. Setup in 2 minutes, works offline.
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 San FranciscoCodex CLI Memory in New York CityCodex CLI Memory in AustinCodex CLI Memory in SeattleCodex CLI Memory in BostonCodex CLI Memory in ChicagoCodex CLI Memory in DenverCodex CLI Memory in Los AngelesCodex CLI Memory in AtlantaCodex CLI Memory in MiamiCodex CLI Memory in DallasCodex CLI Memory in San Diego
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 — 2 MIN SETUP