Rivet can't find my dev server
Rivet can't find my dev server
Start your dev server first (If port 4000 is taken, Rivet moves to the next free port on its own — or pin one with
npm run dev or whatever your project uses), then open Rivet again. Rivet checks the ports common frameworks use; if yours runs somewhere unusual, point at it directly:--rivet-port. Plain HTML projects don’t need a dev server at all: use --framework static (and --entry if your entry file isn’t index.html).Install fails with a Node.js version message
Install fails with a Node.js version message
Rivet needs Node.js 22.13 or newer. Check with
node --version, upgrade, then reinstall with the @latest tag so npm doesn’t hand you an old release:Authentication required / AUTH_REQUIRED errors
Authentication required / AUTH_REQUIRED errors
Run
rivet login in a terminal. It opens a browser sign-in and finishes on its own. If your agent reports an AUTH_REQUIRED error, this is the same fix. Check where you stand with rivet auth status.Git isn't initialized in my project
Git isn't initialized in my project
In an existing project, Rivet uses git to keep each variant’s workspace separate, so the project needs to be a git repository (
git init). To run without any git features, start Rivet with --no-git.The MCP server doesn't show up in my client
The MCP server doesn't show up in my client
Re-run the install for that client (with
--mcp where it applies) and fully restart it:- Cursor — quit and reopen, then check Settings → MCP for a green
rivetentry. - Claude Desktop — confirm a
rivetentry exists inclaude_desktop_config.json(macOS:~/Library/Application Support/Claude/), then restart the app. - Codex CLI — run
cat ~/.codex/config.tomland confirm an[mcp_servers.rivet]section exists.
A variant start seems stuck
A variant start seems stuck
Setting up workspaces can take a few minutes. While
rivet status reports variants.starting: true, the run is still getting ready — don’t cancel or retry, just wait (or watch live with rivet status --watch). If rivet wait <workId> exits with code 5, the work is still running; that’s a timeout, not a failure.How do I see what Rivet is doing?
How do I see what Rivet is doing?
rivet --debugturns on verbose logging.rivet status --watchstreams live session state in the terminal.- Every command prints a JSON result with a stable error code — see exit codes.
- Desktop app logs live at
~/Library/Logs/Rivet/on macOS.

