Developer docs
Install rh and capture your first session.
Capture your coding agents’ sessions into one record you own. Install the runtime, connect a tool and verify your first session.
One command to start
$ curl -fsSL https://get.rivethub.io/local.sh | bashIt verifies the release against its checksums, installs rh into ~/.local/bin and starts a standalone node. On Linux with a usable systemd user session, it hands the node to an enabled rivethub.service; otherwise it explains that the node will not restart by itself. The quickstart carries on from there to a captured session.
One binary, a few jobs
| Part | What it does |
|---|---|
| Capture | rh capture hook, run from a tool’s own hook, posts the session to your node and spools it to disk when the node is down. |
| Gateway | rh local (standalone) or rh gateway (datahub) serves the memory API, the stored sessions and the wiki. |
| Memory | Hybrid search, a tree of summaries per session, topics, decisions, entities and a wiki, built on top of what was captured. The original is always kept. |
| MCP | rh mcp gives any MCP client the node’s memory. |
| Workers | rh worker --role … embeds, summarizes, files and writes the wiki in the background, using a model you choose. |
| Migrations | rivethub-migrate applies every schema change. Postgres services never migrate on start; standalone SQLite migrates automatically. |
rh does not run agents. Live sessions, chat and terminals stay in the tools you already use.
Two ways to run it
One person, one machine
Standalone
Quickstartrh local: one process and one SQLite file at~/.rivethub/memory.sqlite. The fastest way to start.Several machines or people
Datahub
Everyone captures into one Postgres that you run. Row-level security keeps each person’s memory private until they share it.
Datahub
Where to look
Sharing · Keeping the node running · Upgrading · Troubleshooting · Command-line reference · Operations reference · Memory service reference.
Capture
Which tools are supported, what each hook reads, and what happens when the node is down.
CaptureMemory
Search, summaries, topics and the wiki; turning on the workers; exporting and moving your record.
MemoryAPI and MCP
The gateway, its authentication, and the core memory tools agents call.
API and MCPContributing
Build, check and test the runtime, and the rules a change is held to.
Contributing
Start with one captured session.
A few minutes, with no model, no database and no account.