OpenCode

Connect OpenCode to Renor memory: one command, the manual config, the optional capture plugin, and a check that it works.

Renor gives OpenCode one durable memory over MCP. What you tell OpenCode, your other connected agents can recall later, and the other way round.

You need Node 18 or later and a Renor account. Anyone can sign up at https://app.renor.cloud/signup.

​

Connect in one command

npx renor connect --client opencode

It signs you in once in the browser, adds Renor to ~/.config/opencode/opencode.json (your other keys and servers are kept, and Renor is never added twice), installs the Renor skill and writes a short memory rule. Preview first with:

npx renor connect --client opencode --dry-run

Restart OpenCode when it finishes.

​

Connect by hand

Merge this into ~/.config/opencode/opencode.json, keeping every existing key:

{
  "mcp": {
    "renor": { "type": "remote", "url": "https://mcp.renor.cloud/mcp" }
  }
}

Then sign in and restart OpenCode:

opencode mcp auth renor

On a machine with no screen (a server or an SSH session), use an access key instead; see Running on a server.

​

Optional: the capture plugin

npx renor setup --capture
npx renor capture status

If OpenCode is installed, --capture also writes one small file, plugins/renor-capture.js, next to your OpenCode config. It never edits opencode.json. npx renor capture status shows OpenCode plugin ON, OFF or NOT INSTALLED.

To remove it:

npx renor setup --capture --uninstall

​

Check that it works

List the servers OpenCode knows about and confirm renor is there and signed in:

opencode mcp list

Then, in OpenCode, say: “Remember that my staging port is 4310.” Start a new session and ask: “What is my staging port?” It should answer 4310 from Renor. You can also run npx renor status to see which apps are connected and when the last save was.

​

If something goes wrong

• The sign-in page will not finish. OpenCode uses port 19876 for the sign-in callback. Stop any program holding that port, then run opencode mcp auth renor again. Your account already exists, so repeating a timed-out sign-in is safe.
• OpenCode does not mention Renor, or says it has no such tool. Restart OpenCode, then run opencode mcp list and confirm renor is listed and signed in. If it is not signed in, run opencode mcp auth renor.
• A renor entry already exists at a different address. npx renor setup --force replaces it.