01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Antigravity & Gemini Memory · shared project memory
Antigravity & Gemini Memory in Detroit
Gemini-powered IDEs reason brilliantly about the code in front of them; what they cannot know is the history behind it. MemHub feeds Antigravity the decisions, constraints, and postmortems that turn good suggestions into correct ones.
Google-native teams get one more agent to brief. MemHub centralizes that briefing: one synchronized project memory behind Antigravity, Gemini CLI, Claude Code, Cursor, Windsurf, Cline, and Codex alike.
Create your shared memory
Free Community tier. Self-hosted or hosted. No external embedding API required.
acme/antigravity-gemini-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 Detroit engineering teams choose MemHub
In Detroit, software teams ship faster when their tools share one memory instead of three silos. Distributed squads stay aligned because every session opens with the same briefing.
MemHub runs hosted or fully self-hosted, so the storage boundary follows your compliance requirements rather than dictating them.
- Built for Detroit: automotive and mobility software programs.
- 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
Antigravity & Gemini Memory in Detroit, without the trade-offs.
01
Team provenance
Authorship and source links keep agent context accountable.
02
Offline outbox
Local SQLite queues writes through connectivity gaps and syncs safely after.
03
Scoped credentials
Per-project keys with roles and instant revocation.
04
MCP-first
Antigravity and Gemini CLI consume Model Context Protocol servers; MemHub plugs straight in.
05
Multi-model ready
The same memory serves Gemini, Claude, GPT, and local models without duplication.
06
Incremental briefings
Sessions receive deltas since their last sequence — never a stale dump.
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.
What about Gemini CLI?
Gemini CLI reads the same JSON MCP config shape; the connect command writes it for you, or select it as an “other” JSON client.
Does Google Antigravity support MCP servers?
Yes — Antigravity is built around the Model Context Protocol. Point its MCP configuration at the memhub proxy and restart.
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
Antigravity & Gemini Memory in CaliforniaAntigravity & Gemini Memory in TexasAntigravity & Gemini Memory in New York StateAntigravity & Gemini Memory in FloridaAntigravity & Gemini Memory in Washington StateAntigravity & Gemini Memory in MassachusettsAntigravity & Gemini Memory in ColoradoAntigravity & Gemini Memory in IllinoisAntigravity & Gemini Memory in GeorgiaAntigravity & Gemini Memory in ArizonaAntigravity & Gemini Memory in North CarolinaAntigravity & Gemini 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.
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.
THE NEXT SESSION STARTS HERE