01
decision2m
Usar bloqueos consultivos en PostgreSQL
Fuente: Nelson · architecture.md
CODEX CLI MEMORY · AVAILABLE NOW
Codex CLI Memory for engineering teams
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.
N
Nelson · Founder, MemHub at Simplex.lat
Simplex.lat · Quito, Ecuador ·
Written and verified by Nelson at Simplex.lat (Quito, Ecuador) — sources checked August 2026.
Local-first · Offline readySincronización multiagenteSetup en 2 min
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
memorias 41
reglas fijadas 6
colaboradores 9
BRIEFING FOR NEW SESSION
What changed since your last pull
02
pattern18m
Los errores de API siguen RFC 9457
Fuente: Maya · PR #184
03
bugfix1h
Los refresh tokens rotan atómicamente
Fuente: Codex CLI · auth/session.ts
Claude Code
Cursor
Codex CLI
THE MECHANISM
Write once. Every session remembers.
Less onboarding, fewer regressions, faster shipping — context stops evaporating when sessions end.
01
You keep coding
Decisions auto-captured where you work — terminal, PR, editor. No extra docs, no context-switching.
02
MemHub does the plumbing
Local SQLite outbox first, then project-scoped sync with provenance (who, when, why). Works offline.
03
Next session starts ahead
Every teammate and agent opens pre-briefed with only what changed since their last pull.
UNIVERSAL COMPATIBILITY
Plugs into any CLI, IDE, or AI coding agent.
If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires your editors and terminals without friction.
- 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: specific benefits for your team
01
Shell closes, memory doesn’t
Each Codex invocation inherits what changed since last pull — incremental briefing, not amnesia.
02
Take it to any machine
Memory follows you across laptops/containers — not just the current checkout.
03
One insight, whole team
A fix found on your box is on every teammate’s next Codex session — automatically.
04
Keep working on the plane
SQLite outbox queues writes offline and flushes safely later — no work hostage to VPN.
05
Verify before you act
Every entry has author, source, and version — trust but check before the agent runs.
06
Wired in one line
memhub connect --ide codex + mh login — configured securely in seconds.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Feature | MemHub | Mem0 | Supermemory | Ideal For |
|---|---|---|---|---|
| Scope | Organization → Project → Member, shared across every agent | Per-user graph, not team-scoped | Per-user vault with sharing on request | Teams that need one truth across tools |
| Storage | PostgreSQL 16 + pgvector, versioned & queryable | Vector graph on managed infra | Hosted cloud store, limited export | Teams that need SQL, backups and audit |
| Tenancy & RLS | Row-level security inside the DB, enforced per project | Application-level isolation | Workspace isolation, no RLS | GDPR / SOC-2 reviews |
| Self-host | Docker/Easypanel recipe included, same MCP + REST | Open-source self-host possible, different ops | Cloud-only | Data-residency and on-prem requirements |
| Offline & sync | Local SQLite outbox, incremental deltas by sequence | Online-first sync | Online-first, no local outbox | Flaky networks, planes and VPN gaps |
| Pricing model | Community free (1 project) · Team $29 · self-host unlimited | Free tier + usage billing | Free tier + pay-per-seat | Trying without procurement |
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.
memhub-cli · preview
Click tabs to simulateSimulate CLI
$
memhub save --type decision "Usar bloqueos consultivos en Postgres" -m "Evita colisiones concurrentes en el outbox"stdout · [mem_save]12ms
[detect] Contexto resuelto: acme/payments-api
[sqlite] Guardando en outbox local (~/.memhub/outbox.db)...
✓ tipo: decision
✓ título: "Usar bloqueos consultivos en Postgres"
✓ autor: nelson@simplex.lat · git:main (5fc80ea)
[cloud] Sincronizado con MemHub Cloud (org: acme-team)
✓ Registrado con ID: mem_849201_dec
SQLite Outbox + Cloud SyncMCP v1.0
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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
COUNTRIES · Regional Deployments
Codex CLI Memory across United StatesCodex CLI Memory across CanadaCodex CLI Memory across 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 ItalyCodex CLI Memory across NetherlandsCodex CLI Memory across BelgiumCodex CLI Memory across SwitzerlandCodex CLI Memory across AustriaCodex CLI Memory across SwedenCodex CLI Memory across NorwayCodex CLI Memory across DenmarkCodex CLI Memory across FinlandCodex CLI Memory across EstoniaCodex CLI Memory across PolandCodex CLI Memory across CzechiaCodex CLI Memory across RomaniaCodex CLI Memory across MexicoCodex CLI Memory across BrazilCodex CLI Memory across ArgentinaCodex CLI Memory across ChileCodex CLI Memory across ColombiaCodex CLI Memory across PeruCodex CLI Memory across UruguayCodex CLI Memory across Costa RicaCodex CLI Memory across EcuadorCodex CLI Memory across PanamaCodex CLI Memory across GuatemalaCodex CLI Memory across El SalvadorCodex CLI Memory across Dominican RepublicCodex CLI Memory across ParaguayCodex CLI Memory across AustraliaCodex CLI Memory across New ZealandCodex CLI Memory across JapanCodex CLI Memory across South KoreaCodex CLI Memory across SingaporeCodex CLI Memory across IndiaCodex CLI Memory across United Arab EmiratesCodex CLI Memory across IsraelCodex CLI Memory across South AfricaCodex CLI Memory across NigeriaCodex CLI Memory across KenyaCodex CLI Memory across PhilippinesCodex CLI Memory across VietnamCodex CLI Memory across England
US STATES · Regional Deployments
Codex CLI Memory in CaliforniaCodex CLI Memory in TexasCodex CLI Memory in New York StateCodex CLI Memory in FloridaCodex CLI Memory in Washington StateCodex CLI Memory in MassachusettsCodex CLI Memory in ColoradoCodex CLI Memory in IllinoisCodex CLI Memory in GeorgiaCodex CLI Memory in ArizonaCodex CLI Memory in North CarolinaCodex CLI Memory in UtahCodex CLI Memory in OregonCodex CLI Memory in VirginiaCodex CLI Memory in New JerseyCodex CLI Memory in PennsylvaniaCodex CLI Memory in MichiganCodex CLI Memory in TennesseeCodex CLI Memory in MinnesotaCodex CLI Memory in OhioCodex CLI Memory in NevadaCodex CLI Memory in Maryland
PROVINCES & REGIONS · Regional Deployments
CITIES & TECH HUBS · Regional Deployments
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 DiegoCodex CLI Memory in PortlandCodex CLI Memory in PhoenixCodex CLI Memory in PhiladelphiaCodex CLI Memory in NashvilleCodex CLI Memory in MinneapolisCodex CLI Memory in RaleighCodex CLI Memory in Salt Lake CityCodex CLI Memory in DetroitCodex CLI Memory in TorontoCodex CLI Memory in VancouverCodex CLI Memory in MontrealCodex CLI Memory in LondonCodex CLI Memory in ManchesterCodex CLI Memory in EdinburghCodex CLI Memory in DublinCodex CLI Memory in BerlinCodex CLI Memory in MunichCodex CLI Memory in HamburgCodex CLI Memory in ZurichCodex CLI Memory in GenevaCodex CLI Memory in ViennaCodex CLI Memory in ParisCodex CLI Memory in LyonCodex CLI Memory in AmsterdamCodex CLI Memory in RotterdamCodex CLI Memory in BrusselsCodex CLI Memory in MadridCodex CLI Memory in BarcelonaCodex CLI Memory in ValenciaCodex CLI Memory in MálagaCodex CLI Memory in SevilleCodex CLI Memory in BilbaoCodex CLI Memory in ZaragozaCodex CLI Memory in MurciaCodex CLI Memory in Palma de MallorcaCodex CLI Memory in Las Palmas de Gran CanariaCodex CLI Memory in LisbonCodex CLI Memory in PortoCodex CLI Memory in MilanCodex CLI Memory in RomeCodex CLI Memory in StockholmCodex CLI Memory in CopenhagenCodex CLI Memory in OsloCodex CLI Memory in HelsinkiCodex CLI Memory in TallinnCodex CLI Memory in WarsawCodex CLI Memory in KrakówCodex CLI Memory in PragueCodex CLI Memory in BucharestCodex CLI Memory in Mexico CityCodex CLI Memory in GuadalajaraCodex CLI Memory in MonterreyCodex CLI Memory in QuerétaroCodex CLI Memory in PueblaCodex CLI Memory in TijuanaCodex CLI Memory in MéridaCodex CLI Memory in São PauloCodex CLI Memory in Rio de JaneiroCodex CLI Memory in Buenos AiresCodex CLI Memory in CórdobaCodex CLI Memory in RosarioCodex CLI Memory in MendozaCodex CLI Memory in SantiagoCodex CLI Memory in ValparaísoCodex CLI Memory in ConcepciónCodex CLI Memory in BogotáCodex CLI Memory in MedellínCodex CLI Memory in CaliCodex CLI Memory in BarranquillaCodex CLI Memory in QuitoCodex CLI Memory in GuayaquilCodex CLI Memory in LimaCodex CLI Memory in ArequipaCodex CLI Memory in MontevideoCodex CLI Memory in AsunciónCodex CLI Memory in San JoséCodex CLI Memory in Panama CityCodex CLI Memory in Guatemala CityCodex CLI Memory in San SalvadorCodex CLI Memory in Santo DomingoCodex CLI Memory in SydneyCodex CLI Memory in MelbourneCodex CLI Memory in BrisbaneCodex CLI Memory in PerthCodex CLI Memory in AucklandCodex CLI Memory in TokyoCodex CLI Memory in OsakaCodex CLI Memory in SeoulCodex CLI Memory in SingaporeCodex CLI Memory in BengaluruCodex CLI Memory in HyderabadCodex CLI Memory in PuneCodex CLI Memory in MumbaiCodex CLI Memory in Delhi NCRCodex CLI Memory in DubaiCodex CLI Memory in Tel AvivCodex CLI Memory in ManilaCodex CLI Memory in Ho Chi Minh CityCodex CLI Memory in Hong KongCodex CLI Memory in TaipeiCodex CLI Memory in Kuala LumpurCodex CLI Memory in JakartaCodex CLI Memory in BangkokCodex CLI Memory in JohannesburgCodex CLI Memory in Cape TownCodex CLI Memory in LagosCodex CLI Memory in Nairobi
GUIDES, COMPARISONS & PLAYBOOKS
Mem0 Alternative for Teams — MemHub
Best MCP Memory Servers for Teams (2026)
CLAUDE.md vs Shared Team Memory — When You Need Both
How to Share AI Coding Context Across Your Team
Agent Memory Playbook for Agile Teams (2026)
Mem0 vs MemHub: Team AI Memory Compared Guide
Supermemory vs MemHub: Team AI Memory Compared Guide
Letta vs MemHub: Team AI Memory Compared Guide
Cognee vs MemHub: Team AI Memory Compared Guide
Zep vs MemHub: Team AI Memory Compared Guide
Start free — 2 min1 project free · no card requiredGuided demo20 min · see your repo rememberedSelf-host it myselfDocker + pgvector · you own the data
THE NEXT SESSION STARTS HERE — 2 MIN SETUP