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

Before you start

  • Install and authenticate Claude Code in the terminal where you will work.
  • Open the project folder in the same shell where Claude Code 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:
curl -fsSL https://www.byterover.dev/uninstall-v3.sh | sh
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 Claude Code runs: Requires Node.js 20 or newer. Node.js includes npm and npx.
npx skills add campfirein/skills
Run the command in the same environment where Claude Code runs.

Restart Claude Code

Stop the current Claude Code session, then start a new one in the project:
cd path/to/your/project
claude
Agents load installed skills when a new session starts.

Authenticate with ByteRover

Prompt Claude Code:
Authenticate with ByteRover.
Claude Code 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:
approved

Onboard with ByteRover

Prompt Claude Code:
onboard with ByteRover
Claude Code checks whether the project is linked to a ByteRover space.

If Claude Code needs a space

Open ByteRover Desktop, create or select the space for this project, then prompt Claude Code again:
onboard with ByteRover

Verify

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