Skip to main content
ByteRover V4 connects agents through the published ByteRover skill. Install the skill in the same environment where the agent runs, restart the agent, authenticate ByteRover, then start onboarding from inside your project. OpenClaw also supports a V4 setup script that installs the skill and configures the ByteRover context engine. ByteRover and OpenClaw agent integration

​
Setup flow

1

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.
2

Install ByteRover

Requires Node.js 20 or newer. Node.js includes npm and npx.For OpenClaw, run the setup script:
This installs the ByteRover skill and configures the latest ByteRover OpenClaw context engine.To clean up the OpenClaw context engine later, run the same script with the uninstall flag:
For other agents, install the published ByteRover skill:
This installs the published ByteRover skill bundle from campfirein/skills.
3

Restart the agent

Fully quit and reopen the agent so it can load the installed ByteRover skill.
4

Authenticate with ByteRover

Open the URL the agent prints, approve the request in your browser, then return to the agent and type approved.
5

Start ByteRover onboarding

The agent links the project to the right space and begins using durable memory after onboarding.

​
Supported agents

Choose the agent you want to connect.

OpenClaw

Install the skill and context engine, restart OpenClaw, authenticate, and start onboarding.

Hermes

Install the skill, restart Hermes, authenticate, and start onboarding.

Codex CLI

Use ByteRover from Codex CLI on a VPS or remote development machine.

Claude Code

Use ByteRover from Claude Code in a terminal session.

OpenCode CLI

Use ByteRover from OpenCode CLI on a VPS or local terminal.

V3 to V4 VPS migration

Move self-managed V3 project memory on a VPS into V4 spaces.

​
VPS notes

When the agent runs on a VPS, install the ByteRover skill on the VPS, not only on your laptop. The agent reads skills from its own environment. Authenticate before onboarding. If the agent prints a sign-in URL, open that URL in your browser. After you approve it, return to the VPS terminal and type:
If the agent cannot find a space for the project, open ByteRover Desktop, create or select the right space, then prompt the agent again:
If the VPS already has V3 project memory, migrate it before relying on the project in V4:

Migrate V3 VPS data to V4

Detect V3 projects, preview the migration, create V4 spaces, verify the result, then back up and remove old V3 files.