Skip to main content
Example errors:
Agent not initialized: Agent initialization failed: Blob storage initialization error: Fail

Failed to initialize SQLite storage: The module was compiled against a different Node.js version
If you installed via the curl script, this error should not occur because the binary bundles its own runtime. Re-run the install script to fix:
curl -fsSL https://byterover.dev/install.sh | sh
If you installed via npm, this is caused by a Node.js version mismatch — the CLI was installed with a different Node version than what’s currently active.Solution: Use Node.js >= 20 and reinstall:
# Check your Node version (should be v20+)
node --version

# If using nvm, switch to a supported version
nvm install 20 && nvm use 20

# Reinstall ByteRover CLI
npm uninstall -g byterover-cli
npm install -g byterover-cli
After reinstalling, run brv restart to start fresh.
Symptom:A command (like /query) is visibly running in the REPL, but the TUI displays running:0.Cause:This typically happens when:
  • The REPL has been kept active for a long time
  • Your laptop went to sleep mode while the REPL was open
Solution:Run brv restart to stop all processes and start fresh:
brv restart
Alternatively, press Ctrl+C to quit the current session and start a new one with brv.
Run brv status for a quick health check. It shows your CLI version, account state, current space, and context tree status:
brv status
Common status messages and fixes:
MessageFix
”Daemon failed to start automatically”Run brv restart
”Daemon crashed unexpectedly”Run brv restart
”Account: Not connected”Normal for local-only usage — no action needed
If brv restart does not resolve the issue, try reinstalling:
# curl install
curl -fsSL https://byterover.dev/install.sh | sh

# npm install
npm uninstall -g byterover-cli && npm install -g byterover-cli