Skip to main content
When a new version of ByteRover CLI is available, you’ll see a prompt before your command runs:
? Update available: 1.2.0 → 1.2.1. Would you like to update now? (Y/n)
  • Press Enter or type y to update immediately
  • Type n to skip and continue with your command
If you accept the update, your original command will not run. You’ll need to run it again after the update completes.
If the automatic update encounters an error, you’ll see:
Updating byterover-cli...
<npm error output>
⚠️  Automatic update failed. Please run manually: npm update -g byterover-cli
Your original command will still proceed. To update manually, run:
npm update -g byterover-cli
Since re-init will remove the entire .brv directory, and you may have local memories that have not been pushed to remote, please follow these steps carefully before updating:
1

Backup your context tree

Temporarily move your local context tree outside the .brv/ folder:
cp -r .brv/context-tree .
2

Run the update and re-init

After updating, run in the REPL:
/init
Select your team and space.
3

Restore your context tree

Move all folders from the temporary context tree back into .brv/context-tree:
mv context-tree/* .brv/context-tree/
Remove the old snapshot file:
rm .brv/context-tree/.snapshot.json
4

Push your recovered memories

Run:
/status
/push
to upload all recovered local memories.
5

Clean up

Delete the temporary folder once everything is confirmed.