MemHub
Start free — 2 min

Claude Code Memory in · shared project memory — local-first · offline-ready

Claude Code Memory in Nashville

Teach once, everyone benefits. What one dev tells Claude Code, every teammate’s Claude Code knows next run — ranked deltas, not dumps. No card, free for one project.

Keep CLAUDE.md for invariants, let MemHub carry the long tail. Durable Claude Code memory that survives sessions, machines, and months — query in seconds, works offline.

Start free — get briefed in 2 min

Free for 1 project · No card · Self-host or we host · No external API

acme/claude-code-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 Nashville engineering teams choose MemHub

In Nashville, 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.

  • Nashville: 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

Claude Code Memory in Nashville, without the trade-offs.

01

Teach once, everyone benefits

What one dev tells Claude Code, every teammate’s Claude Code knows on next run. No forwarding needed.

02

Lock the non-negotiables

Pin invariants so they outrank newer, noisier memories — agents respect past calls.

03

No lost work on bad Wi-Fi

Local-first outbox queues writes when offline — syncs safely after. Keep coding.

04

Ship in one command

memhub connect writes your Claude Code JSON — no hand-edits, no docs to skim.

05

Escape the CLAUDE.md wall

Structured memories with types/topics/versions — not one markdown file growing forever past 2k tokens.

06

Start ahead, not from scratch

Each session gets only the delta since its last sequence — no repeated boilerplate in your context window.

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 this replace Claude Code auto memory?

No. Auto memory stays useful for personal preferences. MemHub adds the shared, project-scoped layer: cross-machine recall, provenance, and team-wide search.

Will my context window fill up with old memories?

No. Briefings are incremental — sessions receive the delta since their last known sequence, and retrieval is ranked rather than bulk-dumped.

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

Claude Code Memory in CaliforniaClaude Code Memory in TexasClaude Code Memory in New York StateClaude Code Memory in FloridaClaude Code Memory in Washington StateClaude Code Memory in MassachusettsClaude Code Memory in ColoradoClaude Code Memory in IllinoisClaude Code Memory in GeorgiaClaude Code Memory in ArizonaClaude Code Memory in North CarolinaClaude Code 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.

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.

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