01
decision2m
Usar bloqueos consultivos en PostgreSQL
Fuente: Nelson · architecture.md
CURSOR AI MEMORY · AVAILABLE NOW
Cursor Memory in Los Angeles
Teams on Cursor stay aligned without extra docs. One searchable memory per project, identical from Cursor, Claude Code, or the web portal. Free to start, offline-ready.
Keep .cursor/rules for steering, move durable reasoning to shared memory. Ranked retrieval, scoped access, one-command MCP setup — ship faster without re-explaining.
N
Nelson · Founder, MemHub at Simplex.lat
Simplex.lat · Quito, Ecuador ·
Published by MemHub at Simplex.lat. Product limits come from the current plans; validate capabilities in your own pilot.
Local-first · OfflineSin pérdida de contextoSetup 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/cursor-memory
synchronizedcontext/main
memorias 41
fijadas 6
autores 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
Definition
What is Cursor Memory in Los Angeles?
Cursor Memory is how engineering teams preserve the why behind the code — rejected alternatives, pinned invariants and recent fixes — as searchable, versioned entries. In Los Angeles, MemHub delivers that memory over MCP with incremental briefings, offline support and auditable authorship.
Team plan at a glance
$29
Team per workspace per month (USD)
Team plan price; review current terms before subscribing. This is not a savings estimate.
According to MemHub pricing →5
Seats included in Team
Share decisions with authorized teammates. Shared memory is not a replacement for live collaborative chat.
According to MemHub pricing →20
Projects included in Team
Configure project scope and test what each user can retrieve before connecting sensitive repositories.
According to MemHub pricing →What changes the first week
In the first week with Cursor Memory in Los Angeles, sessions stop re-proposing settled decisions because pinned invariants outrank noise during ranked retrieval. According to Authoritas, AI Overviews cut traditional clicks by 58%, so being the cited, extractable source inside the briefing matters more than dumping more tokens.
Standups shrink to real blockers, reviews surface the original rationale in one query, and agents respect hard constraints automatically. Because briefings are deltas, the archive stays a query away rather than a stowaway in every prompt.
Why Los Angeles teams need Cursor Memory
Cursor Memory in Los Angeles helps engineering teams ship faster because every AI coding session opens pre-briefed with only what changed since the last pull, not a full dump. According to Search Engine Journal, 45% of searches now show an AI Overview, so concise, cited memory answers also travel beyond the IDE into generative results.
Distributed squads stay aligned across time zones, new hires ramp in days from searchable precedent, and mixed toolchains stop fragmenting knowledge. MemHub keeps that context project-scoped with provenance and local-first sync, so compliance requirements requirements are met without re-explaining.
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
Cursor Memory: core benefits and capabilities
01
No silos between tools
Same memory feeds Claude Code and Codex — mixed-tool teams stay consistent.
02
Relevant, not everything
Ranked retrieval by topic/recency — agents get the few memories that matter, not a dump.
03
See only what you should
Per-project credentials — contractors and new hires see exactly scoped projects.
04
Browse without the terminal
Web portal to pin, edit, and audit the same corpus — no lock-in to one editor.
05
Stop rewriting rules
Keep tactical .cursor/rules in-repo — move durable why behind them into queryable shared memory.
06
Fresh chat, full context
Yesterday’s decisions brief today’s Cursor New Chat — across chats, worktrees, and machines.
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 MemHub replace .cursorrules?
No. Rules remain the right place for always-on steering. MemHub holds versioned team knowledge — decisions, constraints, postmortems — that rules files were never shaped to carry. The result is fewer regressions, faster onboarding and prompts that carry current, ranked context rather than stale boilerplate repeated across every agent.
How does Cursor connect to it?
Through the Model Context Protocol: add the memhub entry to your MCP configuration once (the connect command does it for you) and restart Cursor. The result is fewer regressions, faster onboarding and prompts that carry current, ranked context rather than stale boilerplate repeated across every agent.
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. The result is fewer regressions, faster onboarding and prompts that carry current, ranked context rather than stale boilerplate repeated across every agent.
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. The result is fewer regressions, faster onboarding and prompts that carry current, ranked context rather than stale boilerplate repeated across every agent.
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. The result is fewer regressions, faster onboarding and prompts that carry current, ranked context rather than stale boilerplate repeated across every agent.
MORE LOCATIONS
Cursor Memory in CaliforniaCursor Memory in TexasCursor Memory in New York StateCursor Memory in FloridaCursor Memory in Washington StateCursor Memory in MassachusettsCursor Memory in ColoradoCursor Memory in IllinoisCursor Memory in GeorgiaCursor Memory in ArizonaCursor Memory in North CarolinaCursor Memory in Utah
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.
Codex CLI Memory
Persistent context for Codex CLI — personal today, shared tomorrow.
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