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.

Stuck during setup

Node and install

rh is not found
The installer puts it in ~/.local/bin. Add that folder to your PATH, 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 with rh status and rh doctor. On Linux, if the node runs as a service, journalctl --user -u rivethub -n 50 shows why it stopped.
rivethub.service restarts every few seconds
Its log says owner lock is held: a node started with rh local --ensure is still running. Run rh service stop and rh stop, wait until rh status says RivetHub is not running, then rh service start.
The node was down while you worked
Nothing is lost. The hooks keep each batch in ~/.rivethub/capture-spool and 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 status to see what is wired. Connect the tool again with rh harness connect <tool>; add --dry-run to 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 exec runs are captured too. Connecting again changes the hooks, so Codex asks once more. rh harness status says whether Codex trusts the hooks.
OpenCode sessions are not captured
Run rh harness status to check whether the installed plug-in is out of date, then run rh harness connect opencode again. OpenCode 2 is the supported version (on older rh, OpenCode 1.x refused the plug-in with failed 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, then rh stop, wait until rh status says RivetHub is not running, then rh service start.
The node is down after rh update (rh 0.8.4)
On Linux, an update run by rh 0.8.4 (fixed in 0.8.5) rewrites rivethub.service to start rh (deleted), which cannot run; the journal says Unable to locate executable. Run rh service restart: it repairs the file and starts the node. Nothing is lost while it was down.
rh harness connect dsh answers with an error (rh 0.8.3 or older)
DeepSeek Harness connects from rh 0.8.4. Run rh update first. The other tools are not affected.
Codex sub-agents not captured (rh 0.8.6 or older)
From 0.8.7, rh captures Codex sub-agents too: after updating, run rh harness connect codex again and trust the hooks once more.
rh update fails
Run the one-line installer again; it replaces the binaries and leaves ~/.rivethub alone. Releases before 0.8.7 were prereleases, which plain rh update on an old rh may not pick; rh update --channel beta does.

Before you write

What to include

  • Your operating system, and the output of rh version and rh 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.