Skip to main content
Use this when your VPS still has ByteRover V3 memory in .brv/context-tree/ and you want to move it into ByteRover V4.

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

If this VPS still has the old V3 CLI, connectors, OpenClaw integration, or Hermes memory provider installed, remove them before setting up the V4 skill:
This removes the 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 replace the migration step for V3 memory data.

​
Install ByteRover skill

Run this on the VPS, in the same environment where your agent runs:
Restart the agent after installation.
The VPS needs Node.js 20 or newer. Node.js includes npm and npx.

​
Authenticate with ByteRover

Ask your agent:
The agent starts ByteRover authentication and prints a browser URL. Open the URL, approve the request, then return to the VPS terminal and type approved when the agent asks. Authentication must finish before migration starts.

​
Migrate data from V3 to V4

Ask your agent:
The agent checks the VPS for V3 projects, previews what will be migrated, then moves the V3 memory into V4 spaces. Each V3 project becomes a V4 space. The old markdown memory is converted into V4 topics.

​
Verify the migration

Ask your agent:
The agent checks the migrated spaces and topic counts. After that, open ByteRover Desktop and confirm the new V4 spaces are available.

​
Cleanup old V3 files

Only cleanup after the V4 spaces are verified. Ask your agent:
The agent backs up the whole V3 .brv/ folder, then removes the original .brv/ from the project. By default, backups are stored in your Documents folder:
The cleanup command also writes a manifest at the backup root:
If the agent uses a custom backup parent, ByteRover still creates a ByteRover_Backups folder inside it:
To restore old V3 files, copy the backed up brv/ folder back to the project as .brv/.