Support
Get help.
Setup questions, something that is not working, or an idea for what RivetHub should do next are all welcome. Most setup problems are one of the few below.
Open an issue
Bugs, questions and ideas live on GitHub, where you can track them.
Open an issue on GitHubEmail us
For setup help or a longer conversation.
rivetphilbot@gmail.comFind us on X
Quick questions, or show us what you are building.
@rivethub
Stuck during setup
Node and install
rhis not found- The installer puts it in
~/.local/bin. Add that folder to yourPATH, or open a new terminal. - Nothing answers on
127.0.0.1:5174 - The node is not running. Start it with
rh local --ensure, then check it withrh statusandrh doctor. On Linux, if the node runs as a service,journalctl --user -u rivethub -n 50shows why it stopped. rivethub.servicerestarts every few seconds- Its log says
owner lock is held: a node started withrh local --ensureis still running. Runrh service stopandrh stop, wait untilrh statussays RivetHub is not running, thenrh service start. - The node was down while you worked
- Nothing is lost. The hooks keep each batch in
~/.rivethub/capture-spooland send it the next time a hook runs with the node up.
Capture and search
- No new line in the capture log
- Run
rh harness statusto see what is wired. Connect the tool again withrh harness connect <tool>; add--dry-runto see what it would change first. Then start a new session in the tool. - Codex sessions are not captured
- Codex runs a hook only after you have trusted it. Open Codex in a terminal; when it says Hooks need review, choose Trust all and continue. After that,
codex execruns are captured too. Connecting again changes the hooks, so Codex asks once more.rh harness statussays whether Codex trusts the hooks. - OpenCode sessions are not captured
- Run
rh harness statusto check whether the installed plug-in is out of date, then runrh harness connect opencodeagain. OpenCode 2 is the supported version (on olderrh, OpenCode 1.x refused the plug-in withfailed to load plugin). - The agent cannot find what you said
- Ask it, in a new session, to search RivetHub memory for an exact phrase. Keyword search needs no model; search by meaning needs an embedding endpoint (setup).
Upgrading from older 0.8.x builds
- Node does not restart after a reboot on Linux (installed before 0.8.3)
- Run the one-line installer again, or run
rh service init, thenrh stop, wait untilrh statussays RivetHub is not running, thenrh service start. - The node is down after
rh update(rh0.8.4) - On Linux, an update run by
rh0.8.4 (fixed in 0.8.5) rewritesrivethub.serviceto startrh (deleted), which cannot run; the journal saysUnable to locate executable. Runrh service restart: it repairs the file and starts the node. Nothing is lost while it was down. rh harness connect dshanswers with an error (rh0.8.3 or older)- DeepSeek Harness connects from
rh0.8.4. Runrh updatefirst. The other tools are not affected. - Codex sub-agents not captured (
rh0.8.6 or older) - From 0.8.7,
rhcaptures Codex sub-agents too: after updating, runrh harness connect codexagain and trust the hooks once more. rh updatefails- Run the one-line installer again; it replaces the binaries and leaves
~/.rivethubalone. Releases before 0.8.7 were prereleases, which plainrh updateon an oldrhmay not pick;rh update --channel betadoes.
Before you write
- The setup guide, including how to check your first captured session.
- How it works for capture, search, summaries and the MCP tools, and the runtime README for every setting.
- Common questions.
What to include
- Your operating system, and the output of
rh versionandrh doctor. - For capture problems: the tool, the output of
rh harness status, and the last lines of its log in~/.rivethub/(for Claude Code,claude-capture.log). - What you tried, and the exact error message if there is one.
Check before you paste. Logs and session text can contain tokens, connection strings and private work. Remove them before you send anything or post it in a public issue.