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

Antigravity & Gemini Memory in Bucharest

Gemini reasons brilliantly on code in front of it; MemHub gives it history behind it — constraints, postmortems, decisions that make good suggestions correct.

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

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
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 Bucharest engineering teams choose MemHub

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

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

Antigravity & Gemini Memory in Bucharest, without the trade-offs.

01

One memory, any model

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

02

Never a stale dump

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

03

Accountable context

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

04

Works through gaps

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

05

Laptop leaves, access dies

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

06

Make Gemini remember

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

The honest comparison.

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

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.

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

EXPLORE OTHER USE CASES

THE NEXT SESSION STARTS HERE — 2 MIN SETUP

Stop rebuilding context.
Start shipping faster.

Create workspace — free