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.

​
Before You Start

Check if you have unpushed local changes: 
brv status
If you see unpushed changes, push them first using the old commands: 
brv push
Optional backup: cp -r .brv/context-tree .brv/context-tree-backup

​
Migrate

1

Clone your space with Git-Semantic

Copy the clone URL from your space on app.byterover.dev, then run:
brv vc clone https://byterover.dev/<team>/<space>.git
2

Set your identity

brv vc config user.name "Your Name"
brv vc config user.email "your@email.com"
3

Verify

brv vc status
brv vc log
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:
Old commandNew command
/push or brv push/vc push or brv vc push
/pull or brv pull/vc pull or brv vc pull
/status or brv status/vc status or brv vc status
/reset or brv reset/vc reset or brv vc reset
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:
brv vc add .
brv vc commit -m "update context"
brv vc push
Your context tree already has a git repo. Remove it and re-clone:
rm -rf .brv/context-tree
brv vc clone https://byterover.dev/<team>/<space>.git
Make sure you’re logged in:
brv login --api-key <your-api-key>