Every agent session, from every machine, in one place you can ask.

relic5 is a small hub you run yourself. Each machine sends it the Claude Code and Codex history it holds. You, and your agents, search it by the words or by the meaning, see it as a map, and read the notes your agents keep.

How it works Get relic5 on GitHub

Open source (AGPL-3.0) · alpha · self-hosted · one server, your private network

illustration · not a real hub

Four steps, all on machines you own.

Nothing goes to a cloud service. The machines talk to the hub over your own private network.

Find
Relic Scan finds every transcript on a machine, in every home, mirror and archive.
Push
Each machine sends its messages, tool calls and thinking to the hub, one file per month, and only what changed.
Index
The hub folds a message pushed by two machines into one, builds a keyword index, and stores a vector for each message.
Ask
Search in the web page, from the command line, or let an agent call the hub's tools while it works.

Find what was said, even when you forgot the words.

Search that suggests

Before you type, the page shows what you searched lately, what is asked most and which repos were busy. After, the sessions behind the hits sit on the left and the message, in its conversation, on the right.

Keyword search where every word must appear, and Thai works inside words
Semantic search by meaning, or both blended
Narrow by time, who spoke, machine, repo or one session
Tool calls, thinking, memory notes and git commits as their own layers

illustration · made-up sessions

See your work as a map.

Sessions placed by meaning

Every session becomes one point, placed by the average of its messages' vectors, so sessions about the same thing sit together. Colour is the repo.

3D you can turn and zoom, or a flat 2D view
Hover to name a point; click to read it or search inside it
Light up sessions by name or repo; the rest dims

illustration · made-up points

The notes your agents keep, as pages

Agents write one-fact memory notes: rules you set, decisions made, where things live. relic5 shows them as a feed you can filter by kind and project. Each note opens as a page with its repo, the session that wrote it, and the real file it lives in, line by line.

And the rest of the hub

Live: the newest messages from every machine as they arrive
Jobs: every push, index and embed, failures and recoveries
Asked: what people and agents searched, and what found nothing

Your agents can ask it too.

relic5 speaks MCP. Register it once on a machine, and an agent can look up what was decided last week before it starts again.

# what an agent sends
relic_search {
  "query": "why did the backup move",
  "semantic": true,
  "horizon": "1m"
}
# → hits with the session, time, repo and a link
relic_show { "id": "relic5://2026-10/…", "before": 3 }

relic_searchwords or meaning, with filters

relic_showone message and its neighbours

relic_sessionssessions by repo and time

relic_sessionone session's turns

relic_statuswhat the hub holds, how fresh

Private by how it is built.

On your serverThe hub runs on one machine you own. There is no hosted version and no account.

On your networkMachines reach it over your own private network. A token is asked on every request from anywhere else.

Nothing leavesNo analytics, no third-party calls. Vectors are made on your own machines.

relic5 is open source, in alpha.

The hub's code is on GitHub under the GNU AGPL v3. Start with Relic Scan on each machine, then run the hub on one server you own; the README has the steps.

relic5 on GitHub Relic Scan