Merv
NisaSign-in
OAuth callback timeout after five minutes, or the browser never opened
OAuth callback timeout after five minutes, or the browser never opened
You’re on a remote machine over SSH; the callback landed on your laptop’s loopback. Forward the port and sign in inside that SSH session:Refresh needs no tunnel afterwards. If
ssh can’t bind 19876, another sign-in on the laptop holds the port. Other clients: forward their callback port. Authenticationproject(action="list") returns nothing
project(action="list") returns nothing
The grant reached no projects. Create one at rapidreview.io/merv or via
project(action="create"), or ask a member to add you. Sign in again choosing All my projects if you want the grant to follow you into new projects.The client asks for a key
The client asks for a key
Native clients don’t need one — manifests are URL-only. Only if a client can’t do MCP OAuth (no browser, CI, OpenHands headless): Settings → MCP keys, then
Authorization: Bearer … / MERV_MCP_KEY. When a project key is still required403 credential_audience_forbidden
403 credential_audience_forbidden
An OAuth access token was used somewhere other than
/mcp. Tokens are audience-confined; use the UI’s own sign-in for /api/….Connection
HTTP 426
HTTP 426
Below the version floor (
/api/meta → min_proxy_version). Update the plugin — commands on each client page.HTTP 401 on the first call
HTTP 401 on the first call
Normal — it starts OAuth discovery. If it repeats after sign-in, the token store is stale: sign in again with the client’s MCP auth command.
HTTP 404 on a project route
HTTP 404 on a project route
Not a member of that project. Membership is the authorization boundary.
Cursor: tools missing or a tool-count warning
Cursor: tools missing or a tool-count warning
Cursor caps around 40 tools across all MCP servers; Merv exposes 41 by default. Turn Storage off for the project (−6 tools) or disable other servers. Dotted-name warnings are harmless.
Hermes: tool names look wrong
Hermes: tool names look wrong
Hermes renames dotted tools (
mcp_merv_workflow_status_and_next). Calls still work.Skills and reviews
The agent doesn't know the workflow
The agent doesn't know the workflow
Skills didn’t load. Plugin clients: reinstall or update. Kilo/OpenCode: new session or
/reload. OpenHands/Replit: paste the skill text — nothing installs there.A review never completes, or the capability expired
A review never completes, or the capability expired
The reviewer must be a separate session; capabilities last one hour. Open the experiment in the UI — its reviews are on the detail page. Ask the agent to call
review.request again (it reissues a capability); on clients without subagents, open a second session and paste the handoff prompt. Reviewer handoffSandboxes and auto-run
sandbox.request answered needs_selection
sandbox.request answered needs_selection
Several hardware options fit; the agent must pick one from the response and request again with its provider-shaped values.
A run shows unknown or lost
A run shows unknown or lost
unknown: the machine died before receipts were read — retained evidence may still settle it, otherwise rerun. lost: receipts were read and no completion sentinel existed. SandboxesThe runner printed a code but the machine never appears
The runner printed a code but the machine never appears
Enter it under Auto-run → Pair a machine. Codes expire;
merv-agent-runner pair prints a fresh one.Settings pending won't clear · a platform is not ready
Settings pending won't clear · a platform is not ready
The runner applies changes at an idle cycle.
~/.merv/bin/merv-client harness shows, per platform, whether the executable resolves; fix with merv-client agent <platform> --command <exe>.