MemHub
Start free — 2 min

Windsurf Memory in Valparaíso · shared project memory — local-first · offline-ready

Windsurf Memory in Valparaíso

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.

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

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

memories 41

pinned 6

contributors 9

BRIEFING FOR NEW SESSION

What changed since your last pull

3 new
01
decision

Standardize on idempotent write endpoints

Source: architecture.md

02
pattern

Repository layer owns every database transaction

Source: pull request #214

03
bugfix

Refresh tokens rotate atomically under load

Source: auth/session.ts

Claude Code
Cursor
Windsurf

WHY IT MATTERS HERE

Why Valparaíso engineering teams choose MemHub

In Valparaíso, software teams ship faster when their tools share one memory instead of three silos. Mixed toolchains stop fragmenting knowledge across vendor-specific stores.

Every entry carries authorship and version history, which keeps both humans and auditors comfortable.

  • Valparaíso: connect Claude Code, Cursor, Windsurf, Cline, Codex CLI, or Antigravity to one shared memory. It also plugs into any CLI that speaks MCP or reads a JSON config.
  • Local-first writes keep sessions productive through outages and travel.
  • One command onboards the whole team: memhub login, then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI, or any JSON client.
Start free — 2 min1 project free · no card requiredGuided demo20 min · see your repo rememberedSelf-host it myselfDocker + pgvector · you own the data

UNIVERSAL COMPATIBILITY

Plugs into any CLI or development tool you use.

If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires the majors; everything else joins as a generic client.

  • 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 in Valparaíso, without the trade-offs.

01

Start with what changed

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

02

VPN drops, work doesn’t

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

03

Know who said it

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

04

Revoke in one click

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

05

Beyond the Cascade chat

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

06

One brain, every editor

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

The honest comparison.

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

Start free — 2 min Talk to the team
Without MemHubWith MemHub
Context lives in heads and DMs → onboarding takes daysStructured, searchable memory → new dev/agent productive in minutes
Every agent re-learns the repo from scratchSessions open pre-briefed with only what changed — zero re-explaining
Rules files cap out at ~2k tokensUnbounded versioned history stays one query away — never cap again
Decisions re-litigated, bugs re-introducedPinned invariants prevent regressions — agents respect past calls

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
repository terminal

$ npm install --global @simplexlat/memhub

$ memhub login

✓ project resolved · context ready · memory synchronized

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.

Will this slow my editor down?

No. The proxy is a lightweight local process; heavy storage and search happen server-side.

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.

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.

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.

MORE LOCATIONS

Windsurf Memory in SantiagoWindsurf Memory in ConcepciónWindsurf 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 Miami

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