Antharmaya Labs · Open source · Hermes plugin

Your agents finally
share one memory.

Every AI coding agent on your machine keeps its own private memory. Memory Bridge reads them all — the conversations you've already had — and gives Hermes one searchable index across every one of them.

install
$curl -fsSL antharmaya.com/memory-bridge/install.sh | bash

9

Agents auto-discovered

0

API keys required

<5ms

Per prefetch()

100%

Local index

The amnesia tax

You've told your agents everything. None of them are listening to each other.

Claude Code knows your architecture. Codex remembers your preferences. Gemini has the project plan. But each one starts every session from zero — and Hermes, your always-on agent, can't see any of it.

×Without Memory Bridge
YouWhat port did I put Postgres on last month?
HermesI don't know — I wasn't there when you set it up.
YouClaude Code knew it yesterday.
HermesI can't see Claude Code's conversations.
With Memory Bridge
YouWhat port did I put Postgres on last month?
HermesLet me check what your other agents remember…
Hermes · via Memory BridgePostgres 16 on port 5433 — decided in the photoselect project, with Claude Code on May 12.
Not another memory SDK

Six things nobody else does.

Retroactive

Remembers what you already said

Other memory tools start recording the day you install them. Memory Bridge reads the conversations already sitting on your disk — every session you've had with Claude Code, Codex, Gemini and the rest — and brings them in on day one.

The Brain

A context graph, not just a list

Memory Bridge builds a local graph of your projects, tools, decisions and files — and recalls associatively. Ask “what did I do with Claude Code last week,” or get a live brief on any project: its decisions, outcomes, connected tools, and key files, in one block.

Drift-proof

The LLM never touches the truth

Facts are atomic, dated, and source-linked. Briefings are computed live from those facts — never a stored, mutated summary — so they can't drift, hallucinate, or go stale. Reflection only ever adds; it never overwrites.

Hybrid retrieval

Lexical + graph + (optional) semantic

Typo-tolerant FTS5 trigram search, associative graph recall, and optional local embeddings — fused with Reciprocal Rank Fusion. Sub-millisecond, no vector database, no cloud. Semantic is a single optional install, never required.

Any agent (MCP)

Not just for Hermes

Ships a zero-dependency MCP server, so Claude Desktop, Cursor, Codex — any MCP client — can query the same unified index. One brain, every agent you run.

Zero-config & local

No API key. Nothing leaves.

Deep extraction uses ctx.llm — Hermes' own model — so there's no second key to manage. The index is a local SQLite file that never leaves your machine. No telemetry, no account.

The decision loop

It doesn't just remember facts. It remembers your decisions — and whether they worked.

Every architecture call, every trade-off, every "we'll go with X" gets extracted, attributed to the framework that shaped it, and tracked through to its outcome.

01

Decide

You make a call — a framework, an architecture, a trade-off — across any of your agents.

02

Remember

Memory Bridge extracts the decision, attributes the framework that shaped it, and files it with its rationale and confidence.

03

Verify

Later, mark how it actually turned out. Your agents stop repeating decisions that already failed.

$ hermes memory-bridge decisions --unverified

Auto-discovered on your machine — no hooks, no setup

Claude CodeCodexGeminiCursorOpenCodeGooseContinue.devAiderAgent Linux Control+ your scanner →
How it works

Scan. Extract. Index. Retrieve.

01

Scan

Auto-discovers every agent history on disk — 9 agents, no hooks, no instrumentation.

02

Extract

Rules-based extraction is free and instant; an optional ctx.llm pass adds deep semantic facts.

03

Index

SQLite + FTS5 trigram. Sub-millisecond, typo-tolerant, zero external services.

04

Retrieve

Every turn, relevant memory is injected via hybrid recall (lexical + graph + optional semantic). Or any MCP client queries it directly.

histories → scanner → extractor → SQLite + FTS5 → Hermes, every turn

Install

Live in under a minute.

No external services. No API keys. No telemetry. Python 3.11+ and Hermes 0.16+.

Curl

recommended
curl -fsSL https://antharmaya.com/memory-bridge/install.sh | bash

Clones into ~/.hermes/plugins/memory/, installs deps, runs the first scan.

Git clone

manual
git clone https://github.com/antharmaya/mem-bridge.git \
  ~/.hermes/plugins/memory/antharmaya-bridge

Memory providers live in ~/.hermes/plugins/memory/<name>/ — the Hermes discovery convention.

Activate

hermes
hermes memory setup

Select "antharmaya-bridge", or set memory.provider in ~/.hermes/config.yaml.

Give Hermes the memory your agents already earned.

MIT licensed · Built by Antharmaya Labs · Made in India