01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Coding Agent Context in · shared project memory
Coding Agent Context in Tokyo
The best teams treat prompts like production systems. MemHub adds the missing substrate — durable memory with sequences, cursors, and acknowledgements — so every agent session starts from an accurate, minimal briefing.
Long-context windows didn’t remove the need for curation; they raised its ROI. MemHub decides what enters the window: recent decisions, pinned invariants, relevant precedents — and leaves the archive a query away.
Create your shared memory
Free Community tier. Self-hosted or hosted. No external embedding API required.
acme/coding-agent-context
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 Tokyo engineering teams choose MemHub
In Tokyo, 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.
- Built for Tokyo: enterprise modernization programs at national scale.
- 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
Coding Agent Context in Tokyo, without the trade-offs.
01
Observable
`mh status` and doctor diagnostics show pending events, sequences, and connectivity at a glance.
02
Tool-agnostic
The same context pipeline serves IDE agents, CLI agents, and CI automations alike.
03
Delta delivery
Monotonic sequences and per-device cursors mean sessions fetch only new context.
04
Ranked retrieval
Topic keys and scoring surface the few memories that matter for the task at hand.
05
Deterministic replay
Sync events are immutable and ordered — reconstruct any device’s context state exactly.
06
Token-aware
Briefings stay compact by design; the archive never rides along “just in case”.
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.
Isn’t a bigger context window enough?
Larger windows raise cost and dilute attention. Curated, incremental memory consistently beats raw dumps — the agents act on fewer, more relevant facts.
How do I know agents are in sync?
Each device tracks its own cursor; the status command reports pending events and the last acknowledged sequence per machine.
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
Coding Agent Context in OsakaCoding Agent Context in San FranciscoCoding Agent Context in New York CityCoding Agent Context in AustinCoding Agent Context in SeattleCoding Agent Context in BostonCoding Agent Context in ChicagoCoding Agent Context in DenverCoding Agent Context in Los AngelesCoding Agent Context in AtlantaCoding Agent Context in MiamiCoding Agent Context in Dallas
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.
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