MemHub
Start free — 2 min

WINDSURF AI MEMORY · AVAILABLE NOW

Windsurf Memory in Helsinki

Mixing Windsurf with Claude Code shouldn’t mean two brains. One synchronized MemHub memory with per-project credentials keeps all agents aligned — no silos.

Rules steer the current window; MemHub remembers why. Rejected designs, incident lessons, env quirks brief every new session automatically — works offline, syncs later.

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/windsurf-memory
synchronized

context/main

memorias 41

fijadas 6

autores 9

BRIEFING FOR NEW SESSION

What changed since your last pull

3 new
01
decision2m

Usar bloqueos consultivos en PostgreSQL

Fuente: Nelson · architecture.md

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 Windsurf Memory in Helsinki?

Windsurf Memory is the durable project memory that survives restarts, device switches and session closes so agents inherit what humans already decided. Teams in Helsinki 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 Windsurf Memory without trade-offs

MemHub delivers Windsurf Memory in Helsinki 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 Windsurf Memory in Helsinki, 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

Windsurf Memory: core benefits and capabilities

01

One brain, every editor

Same memory serves Claude Code, Cursor, Codex — no per-editor silos, no drift.

02

Start with what changed

Incremental deltas since last acknowledged sequence — never a stale dump in the prompt.

03

VPN drops, work doesn’t

Local outbox queues writes through tunnel issues and flights — syncs later safely.

04

Know who said it

Provenance on every note — authorship and source link keep context trustworthy.

05

Revoke in one click

Scoped, hashed, revocable keys — a departed laptop loses access instantly.

06

Beyond the Cascade chat

Windsurf’s chat forgets; MemHub over MCP doesn’t — conventions persist beyond any single session.

The honest comparison.

No feature-matrix gymnastics — just what changes the week you adopt MemHub.

Start free — 2 min Talk to the team
FeatureMemHubMem0SupermemoryIdeal For
ScopeOrganization → Project → Member, shared across every agentPer-user graph, not team-scopedPer-user vault with sharing on requestTeams that need one truth across tools
StoragePostgreSQL 16 + pgvector, versioned & queryableVector graph on managed infraHosted cloud store, limited exportTeams that need SQL, backups and audit
Tenancy & RLSRow-level security inside the DB, enforced per projectApplication-level isolationWorkspace isolation, no RLSGDPR / SOC-2 reviews
Self-hostDocker/Easypanel recipe included, same MCP + RESTOpen-source self-host possible, different opsCloud-onlyData-residency and on-prem requirements
Offline & syncLocal SQLite outbox, incremental deltas by sequenceOnline-first syncOnline-first, no local outboxFlaky networks, planes and VPN gaps
Pricing modelCommunity free (1 project) · Team $29 · self-host unlimitedFree tier + usage billingFree tier + pay-per-seatTrying 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.

Start free — 2 min Talk to the team
memhub-cli · preview
Simulate 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.

Will this slow my editor down?

No. The proxy is a lightweight local process; heavy storage and search happen server-side. 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

Does Windsurf support MCP memory servers?

Yes — Windsurf speaks the Model Context Protocol. MemHub exposes memory over stdio through its local proxy, configured in minutes. 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

Windsurf Memory in San FranciscoWindsurf Memory in New York CityWindsurf Memory in AustinWindsurf Memory in SeattleWindsurf Memory in BostonWindsurf Memory in ChicagoWindsurf Memory in DenverWindsurf Memory in Los AngelesWindsurf Memory in AtlantaWindsurf Memory in MiamiWindsurf Memory in DallasWindsurf 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.

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.

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

Stop rebuilding context.
Start shipping faster.

Create workspace — free