01
decision2m
Usar bloqueos consultivos en PostgreSQL
Fuente: Nelson · architecture.md
CLINE MEMORY · AVAILABLE NOW
Cline Memory in Pennsylvania
From conventions to customer constraints, everything Cline learns becomes searchable, auditable capital — available to the next task instantly. No plugin, no fork.
Stop starting every Cline task amnesiac. MemHub gives Cline memory that survives tasks, machines and teammates — durable MCP store the rest of your team already uses.
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/cline-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 Cline Memory in Pennsylvania?
Cline Memory is the durable project memory that survives restarts, device switches and session closes so agents inherit what humans already decided. Teams in Pennsylvania run MemHub on PostgreSQL 16 with pgvector and row-level security, giving every agent the same cited context without vendor lock-in or re-explaining.
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 →How MemHub delivers Cline Memory without trade-offs
MemHub delivers Cline Memory in Pennsylvania by writing first to a local SQLite outbox and then syncing incremental deltas by monotonic sequence, so flaky VPNs never block work. According to the Princeton GEO study, citing sources lifts AI-answer visibility by up to 40%, which structured, provenance-rich memories are built to earn.
Provisioning is one command: memhub login then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI or any JSON MCP client. Row-level security, hashed credentials and an audit trail keep the store team-safe whether you self-host on PostgreSQL 16 or let us host it.
What changes the first week
In the first week with Cline Memory in Pennsylvania, 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.
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
Cline Memory: core benefits and capabilities
01
Cline teaches the team
What Cline discovers, every agent on the team knows — zero handoff meetings.
02
Hard constraints hold
Pin non-negotiables — autonomous runs respect them, fewer dangerous surprises.
03
No fork, no plugin
Standard MCP transport — Cline’s built-in client just works.
04
Offline doesn’t block
Entries queue locally and flush on reconnect — work continues anywhere.
05
Oversight before spread
Review what agents wrote in the human portal before it propagates team-wide.
06
Tasks build on each other
Finished work updates memory; next autonomous task inherits without manual summaries.
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.
Can I limit what Cline writes?
Credentials carry roles and scopes; use reader-scope keys where you want lookup without mutation. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions
How does Cline connect to MemHub?
Through MCP configuration pointing at the memhub proxy — the interactive installer writes it for you. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.
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. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.
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. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.
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. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.
MORE LOCATIONS
Cline Memory in CaliforniaCline Memory in TexasCline Memory in New York StateCline Memory in FloridaCline Memory in Washington StateCline Memory in MassachusettsCline Memory in ColoradoCline Memory in IllinoisCline Memory in GeorgiaCline Memory in ArizonaCline Memory in North CarolinaCline 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.
Cursor Memory
Carry Cursor context across sessions, machines, and teammates.
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.
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