WINDSURF AI MEMORY · AVAILABLE NOW

Windsurf Memory for engineering teams

Stop losing Cascade context every chat. MemHub gives Windsurf persistent memory over MCP — conventions and decisions persist beyond any single Windsurf session. One JSON block, restart, done.

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

context/main

memorias 41

reglas fijadas 6

colaboradores 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

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: specific benefits for your team

01

Beyond the Cascade chat

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

02

One brain, every editor

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

03

Start with what changed

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

04

VPN drops, work doesn’t

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

05

Know who said it

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

06

Revoke in one click

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

The honest comparison.

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

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.

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.

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. 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.

Will this slow my editor down?

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

Windsurf Memory across United StatesWindsurf Memory across CanadaWindsurf Memory across United KingdomWindsurf Memory across IrelandWindsurf Memory across GermanyWindsurf Memory across FranceWindsurf Memory across SpainWindsurf Memory across PortugalWindsurf Memory across ItalyWindsurf Memory across NetherlandsWindsurf Memory across BelgiumWindsurf Memory across SwitzerlandWindsurf Memory across AustriaWindsurf Memory across SwedenWindsurf Memory across NorwayWindsurf Memory across DenmarkWindsurf Memory across FinlandWindsurf Memory across EstoniaWindsurf Memory across PolandWindsurf Memory across CzechiaWindsurf Memory across RomaniaWindsurf Memory across MexicoWindsurf Memory across BrazilWindsurf Memory across ArgentinaWindsurf Memory across ChileWindsurf Memory across ColombiaWindsurf Memory across PeruWindsurf Memory across UruguayWindsurf Memory across Costa RicaWindsurf Memory across EcuadorWindsurf Memory across PanamaWindsurf Memory across GuatemalaWindsurf Memory across El SalvadorWindsurf Memory across Dominican RepublicWindsurf Memory across ParaguayWindsurf Memory across AustraliaWindsurf Memory across New ZealandWindsurf Memory across JapanWindsurf Memory across South KoreaWindsurf Memory across SingaporeWindsurf Memory across IndiaWindsurf Memory across United Arab EmiratesWindsurf Memory across IsraelWindsurf Memory across South AfricaWindsurf Memory across NigeriaWindsurf Memory across KenyaWindsurf Memory across PhilippinesWindsurf Memory across VietnamWindsurf Memory across England

CITIES & TECH HUBS · Regional Deployments

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 DiegoWindsurf Memory in PortlandWindsurf Memory in PhoenixWindsurf Memory in PhiladelphiaWindsurf Memory in NashvilleWindsurf Memory in MinneapolisWindsurf Memory in RaleighWindsurf Memory in Salt Lake CityWindsurf Memory in DetroitWindsurf Memory in TorontoWindsurf Memory in VancouverWindsurf Memory in MontrealWindsurf Memory in LondonWindsurf Memory in ManchesterWindsurf Memory in EdinburghWindsurf Memory in DublinWindsurf Memory in BerlinWindsurf Memory in MunichWindsurf Memory in HamburgWindsurf Memory in ZurichWindsurf Memory in GenevaWindsurf Memory in ViennaWindsurf Memory in ParisWindsurf Memory in LyonWindsurf Memory in AmsterdamWindsurf Memory in RotterdamWindsurf Memory in BrusselsWindsurf Memory in MadridWindsurf Memory in BarcelonaWindsurf Memory in ValenciaWindsurf Memory in MálagaWindsurf Memory in SevilleWindsurf Memory in BilbaoWindsurf Memory in ZaragozaWindsurf Memory in MurciaWindsurf Memory in Palma de MallorcaWindsurf Memory in Las Palmas de Gran CanariaWindsurf Memory in LisbonWindsurf Memory in PortoWindsurf Memory in MilanWindsurf Memory in RomeWindsurf Memory in StockholmWindsurf Memory in CopenhagenWindsurf Memory in OsloWindsurf Memory in HelsinkiWindsurf Memory in TallinnWindsurf Memory in WarsawWindsurf Memory in KrakówWindsurf Memory in PragueWindsurf Memory in BucharestWindsurf Memory in Mexico CityWindsurf Memory in GuadalajaraWindsurf Memory in MonterreyWindsurf Memory in QuerétaroWindsurf Memory in PueblaWindsurf Memory in TijuanaWindsurf Memory in MéridaWindsurf Memory in São PauloWindsurf Memory in Rio de JaneiroWindsurf Memory in Buenos AiresWindsurf Memory in CórdobaWindsurf Memory in RosarioWindsurf Memory in MendozaWindsurf Memory in SantiagoWindsurf Memory in ValparaísoWindsurf Memory in ConcepciónWindsurf Memory in BogotáWindsurf Memory in MedellínWindsurf Memory in CaliWindsurf Memory in BarranquillaWindsurf Memory in QuitoWindsurf Memory in GuayaquilWindsurf Memory in LimaWindsurf Memory in ArequipaWindsurf Memory in MontevideoWindsurf Memory in AsunciónWindsurf Memory in San JoséWindsurf Memory in Panama CityWindsurf Memory in Guatemala CityWindsurf Memory in San SalvadorWindsurf Memory in Santo DomingoWindsurf Memory in SydneyWindsurf Memory in MelbourneWindsurf Memory in BrisbaneWindsurf Memory in PerthWindsurf Memory in AucklandWindsurf Memory in TokyoWindsurf Memory in OsakaWindsurf Memory in SeoulWindsurf Memory in SingaporeWindsurf Memory in BengaluruWindsurf Memory in HyderabadWindsurf Memory in PuneWindsurf Memory in MumbaiWindsurf Memory in Delhi NCRWindsurf Memory in DubaiWindsurf Memory in Tel AvivWindsurf Memory in ManilaWindsurf Memory in Ho Chi Minh CityWindsurf Memory in Hong KongWindsurf Memory in TaipeiWindsurf Memory in Kuala LumpurWindsurf Memory in JakartaWindsurf Memory in BangkokWindsurf Memory in JohannesburgWindsurf Memory in Cape TownWindsurf Memory in LagosWindsurf Memory in Nairobi
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

Stop rebuilding context.
Start shipping faster.

Create workspace — free