Cross-Agent Memory across Paraguay · shared project memory — local-first · offline-ready

Cross-Agent Memory across Paraguay

Switching tools mid-task shouldn’t reset what you taught. With MemHub, context travels with the project — not the vendor. No lock-in, one search surface.

Replace handoff markdowns with governed memory — versioned, searchable, permission-checked. Interactive installer wires every client at once. Self-host free.

Start free — get briefed in 2 min

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

acme/cross-agent-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 Paraguay engineering teams choose MemHub

Across Paraguay, 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.

Teams operating under Law 6534 can point at a concrete architecture instead of promises.

Paraguay: 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.
Data residency you control — run MemHub on infrastructure inside Paraguay or let us host it.
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

Cross-Agent Memory across Paraguay, without the trade-offs.

One memory, every agent

Vendor-neutral store — a constraint taught to Claude Code constrains Cursor and Codex too.

All agents agree

Every client gets same incremental delta — no drift between tools on same repo.

Trace, don’t overwrite

Versioned entries show how a decision evolved — no silent overwrites, no lost rationale.

One search, every lesson

Single query surface across everything any agent learned on any machine — find in seconds.

Roll out in minutes

Interactive installer wires all supported clients at once — or pick just two.

Adopt the next agent free

Standard MCP on the wire — adding Antigravity or Gemini next month needs zero migration.

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.

Which tools share the memory?

Anything that speaks MCP: Claude Code, Cursor, Codex CLI, Google Antigravity, Cline, Windsurf, or a generic JSON-configured client.

Do all agents get write access?

Credentials are scoped per project and role. You decide which machines can read, write, or administer shared memory.

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

Cross-Agent Memory across the United States Cross-Agent Memory across Canada Cross-Agent Memory across the United Kingdom Cross-Agent Memory across Ireland Cross-Agent Memory across Germany Cross-Agent Memory across France Cross-Agent Memory across Spain Cross-Agent Memory across Portugal Cross-Agent Memory across Italy Cross-Agent Memory across the Netherlands Cross-Agent Memory across Belgium Cross-Agent Memory across Switzerland

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.

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