01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Windsurf Memory in Chicago · shared project memory
Windsurf Memory in Chicago
Rules files steer Windsurf inside the current window; MemHub remembers the reasoning — rejected designs, incident lessons, environment quirks — and re-briefs every new session automatically.
Onboarding and handoffs stop hurting when context outlives sessions. Connect Windsurf once via its MCP configuration and the whole team’s history becomes retrievable context.
Create your shared memory
Free Community tier. Self-hosted or hosted. No external embedding API required.
acme/windsurf-memory
synchronizedcontext/main
memories 41
pinned 6
contributors 9
BRIEFING FOR NEW SESSION
What changed since your last pull
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
LOCAL FIT
Why Chicago engineering teams choose MemHub
In Chicago, software teams ship faster when their tools share one memory instead of three silos. New engineers ramp in days because precedent is searchable, not oral history.
Because writes land locally first and synchronize later, flaky connections never block the work.
- Chicago: 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.
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 Chicago, without the trade-offs.
01
Provenance on every note
Authorship and source links keep agent context trustworthy.
02
Revocable credentials
Scoped API keys mean a departed laptop loses access instantly.
03
MCP-native
Windsurf consumes Model Context Protocol servers; add one JSON block and restart.
04
Shared with every tool
The same memory serves Cursor, Claude Code, and Codex CLI — no per-editor silos.
05
Incremental briefings
Sessions pull only what changed since their last acknowledged sequence.
06
Offline-safe
A local outbox queues writes through tunnel dropouts and flights.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Status quo | With MemHub |
|---|---|
| Context lives in heads and DMs | Memory is structured, shared, and searchable |
| Every agent re-learns the repo | Sessions open pre-briefed with only what changed |
| Rules files cap out at ~2k tokens | Unbounded versioned history stays one query away |
Connect the tools already in your repository.
One command injects configuration for Claude Code, Cursor, Codex CLI, Google Antigravity, Windsurf, Cline, or any JSON MCP client.
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 CaliforniaWindsurf Memory in TexasWindsurf Memory in New York StateWindsurf Memory in FloridaWindsurf Memory in Washington StateWindsurf Memory in MassachusettsWindsurf Memory in ColoradoWindsurf Memory in IllinoisWindsurf Memory in GeorgiaWindsurf Memory in ArizonaWindsurf Memory in North CarolinaWindsurf 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.
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