Skip to main content
This guide is for existing users who have context trees created before Git-Semantic was introduced. New users should start with the Getting Started guide instead.

​
Prerequisites

Before starting, make sure you have:
  1. Logged in to the ByteRover CLI:
  2. Configured a team and space — your current team/space is read from brv status. If you haven’t set one up yet, follow the Getting Started guide first.

​
Automated Migration Script

An interactive script that handles backup, push, and clone in one go.
The script will:
  1. Backup your context tree to .brv/context-tree-backup
  2. Push any unpushed changes to the cloud
  3. Clone your space with Git-Semantic version control
If anything fails, the script automatically rolls back to your backup.

​
Manual Migration

If you prefer to migrate manually, follow the steps below.
1

Check for unpushed changes

If you see unpushed changes, push them first using the old commands:
Optionally, back up your context tree:
2

Clone your space with Git-Semantic

Copy the clone URL from your space on app.byterover.dev, then run:
3

Set your identity

4

Verify

You should see a clean working tree and your commit history.
That’s it — you’re on Git-Semantic version control now.

​
What Changes

Old snapshot commands are replaced by vc commands: Once version control is initialized (.brv/context-tree/.git exists), the legacy brv push and brv pull commands are blocked and will throw a VC_GIT_INITIALIZED error. This only affects the migrated project — other projects without Git-Semantic still use the old commands normally.

​
Troubleshooting

Cause: You ran legacy brv push or brv pull on a project that has Git-Semantic version control initialized.Solution: Use the new brv vc push and brv vc pull commands instead:
Your context tree already has a git repo. Remove it and re-clone:
Make sure you’re logged in: