Antigravity & Gemini Memory · shared project memory — local-first · offline-ready

Antigravity & Gemini Memory in Mérida

Multi-model future, one memory. Antigravity, Gemini CLI, Claude Code, Cursor, Cline, Codex — one synchronized, versioned, permission-checked store via standard MCP.

Whatever Google ships next, your memory stays put — SQLite outbox, scoped keys, incremental deltas. No vendor format, zero migration.

Start free — get briefed in 2 min

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

acme/antigravity-gemini-memory

synchronized

context/main

memories 41

pinned 6

contributors 9

BRIEFING FOR NEW SESSION

What changed since your last pull

3 new

decision

Standardize on idempotent write endpoints

Source: architecture.md

pattern

Repository layer owns every database transaction

Source: pull request #214

bugfix

Refresh tokens rotate atomically under load

Source: auth/session.ts

Claude Code

Cursor

Windsurf

WHY IT MATTERS HERE

Why Mérida engineering teams choose MemHub

In Mérida, 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.

Mérida: 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 required Guided demo20 min · see your repo remembered Self-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

Antigravity & Gemini Memory in Mérida, without the trade-offs.

Make Gemini remember

Antigravity/Gemini CLI over MCP — reasoning that’s consistent week-over-week, not per-session.

One memory, any model

Gemini, Claude, GPT, local models — same versioned store, no duplication.

Never a stale dump

Sessions get deltas since last sequence — curated, minimal briefing.

Accountable context

Authorship + source links — check before an agent acts, fewer hallucinations.

Works through gaps

Local SQLite outbox — connectivity blips don’t cost context.

Laptop leaves, access dies

Per-project keys with roles + instant revocation — least privilege by default.

The honest comparison.

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

Start free — 2 min Talk to the team

Without MemHub	With MemHub
Context lives in heads and DMs → onboarding takes days	Structured, searchable memory → new dev/agent productive in minutes
Every agent re-learns the repo from scratch	Sessions open pre-briefed with only what changed — zero re-explaining
Rules files cap out at ~2k tokens	Unbounded versioned history stays one query away — never cap again
Decisions re-litigated, bugs re-introduced	Pinned 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 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 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.

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 Mexico City Antigravity & Gemini Memory in Guadalajara Antigravity & Gemini Memory in Monterrey Antigravity & Gemini Memory in Querétaro Antigravity & Gemini Memory in Puebla Antigravity & Gemini Memory in Tijuana Antigravity & Gemini Memory in San Francisco Antigravity & Gemini Memory in New York City Antigravity & Gemini Memory in Austin Antigravity & Gemini Memory in Seattle Antigravity & Gemini Memory in Boston Antigravity & Gemini Memory in Chicago

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 — 2 MIN SETUP

Stop rebuilding context.
Start shipping faster.

Create workspace — free