Usar bloqueos consultivos en PostgreSQL
Fuente: Nelson · architecture.md
CLAUDE CODE MEMORY · AVAILABLE NOW
Stop babysitting a 2,000-token CLAUDE.md. MemHub gives Claude Code real memory — decisions and fixes persist as structured, versioned memories the whole team shares. Setup in one command.
Nelson · Founder, MemHub at Simplex.lat
Simplex.lat · Quito, Ecuador ·
Written and verified by Nelson at Simplex.lat (Quito, Ecuador) — sources checked August 2026.
Free for 1 project · No card · Self-host or we host · No external API
context/main
memorias 41
reglas fijadas 6
colaboradores 9
BRIEFING FOR NEW SESSION
Fuente: Nelson · architecture.md
Fuente: Maya · PR #184
Fuente: Codex CLI · auth/session.ts
THE MECHANISM
Less onboarding, fewer regressions, faster shipping — context stops evaporating when sessions end.
Decisions auto-captured where you work — terminal, PR, editor. No extra docs, no context-switching.
Local SQLite outbox first, then project-scoped sync with provenance (who, when, why). Works offline.
Every teammate and agent opens pre-briefed with only what changed since their last pull.
UNIVERSAL COMPATIBILITY
If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires your editors and terminals without friction.
WHAT YOU GET
Structured memories with types/topics/versions — not one markdown file growing forever past 2k tokens.
Each session gets only the delta since its last sequence — no repeated boilerplate in your context window.
What one dev tells Claude Code, every teammate’s Claude Code knows on next run. No forwarding needed.
Pin invariants so they outrank newer, noisier memories — agents respect past calls.
Local-first outbox queues writes when offline — syncs safely after. Keep coding.
memhub connect writes your Claude Code JSON — no hand-edits, no docs to skim.
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 |
One command for Claude Code, Cursor, Codex, Windsurf, Cline or any MCP client. No new editor. Setup in 2 minutes, works offline.
memhub save --type decision "Usar bloqueos consultivos en Postgres" -m "Evita colisiones concurrentes en el outbox"No. Auto memory stays useful for personal preferences. MemHub adds the shared, project-scoped layer: cross-machine recall, provenance, and team-wide search. 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.
No. Briefings are incremental — sessions receive the delta since their last known sequence, and retrieval is ranked rather than bulk-dumped. 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.
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.
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.
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.
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
THE NEXT SESSION STARTS HERE — 2 MIN SETUP