Skip to main content
Use the published ByteRover skill to give OpenCode CLI access to persistent project memory from a VPS, remote shell, or local terminal.

​
Before you start

  • Install and authenticate OpenCode CLI in the terminal where you will work.
  • Open the project folder in the same shell where OpenCode CLI runs.

​
Optional step 0: Remove old V3 CLI, connectors, and integrations

If this environment still has the old V3 CLI, connectors, OpenClaw integration, or Hermes memory provider installed, remove them before setting up the V4 skill:
This removes old V3 command-line tools and connectors. It also removes the old OpenClaw integration and Hermes memory provider when they are detected. It does not migrate V3 memory data.

​
Install the ByteRover skill

Run this in the terminal environment where OpenCode CLI runs: Requires Node.js 20 or newer. Node.js includes npm and npx.
Run the command in the same environment where OpenCode CLI runs.

​
Restart OpenCode CLI

Stop the current OpenCode session, then start a new one in the project:
Agents load installed skills when a new session starts.

​
Authenticate with ByteRover

Prompt OpenCode CLI:
OpenCode CLI may print a browser URL and ask you to approve the connection.
  1. Open the URL in your browser.
  2. Approve the request before the code expires.
  3. Return to the terminal.
  4. Type:

​
Onboard with ByteRover

Prompt OpenCode CLI:
OpenCode CLI checks whether the project is linked to a ByteRover space.

​
If OpenCode CLI needs a space

Open ByteRover Desktop, create or select the space for this project, then prompt OpenCode CLI again:

​
Verify

Ask OpenCode CLI to check ByteRover before starting work:
After setup, OpenCode CLI should query memory before non-trivial work and record useful project knowledge when work is complete.

​
Next steps

Query

Learn in depth how the agent retrieves project memory.

Record

Learn in depth how the agent saves durable knowledge.

Space

Manage where this project’s memory lives.