Skip to main content
ByteRover CLI runs entirely on your machine with no cloud account required. Cloud features layer on top — adding team sync, multi-machine access, and backup — without changing the core local workflow.

​
Commands: local vs cloud

Commands available in the interactive REPL (brv):
Works locally (no auth)Requires cloud auth
/status — show local project state/login — authenticate with ByteRover
/locations — list registered projects/logout — clear authentication
/curate — add context to local knowledge tree/vc push — push commits to cloud
/query — query local context tree/vc pull — pull commits from cloud
/connectors — manage agent connectors/vc clone — clone a remote space
/hub — browse and install skills & bundles/vc fetch — fetch remote refs
/providers — connect and switch LLM providers *
/model — select a model *
/vc init — initialize version control
/vc config — set commit author identity
/vc add — stage files
/vc commit — save staged changes
/vc status — show working tree status
/vc log — show commit history
/vc branch — manage branches
/vc checkout — switch branches
/vc merge — merge branches
/vc reset — unstage files or undo commits
/vc remote — manage remote connection
/new — start a fresh session
* Provider and model commands work locally for third-party providers. However, selecting or switching to the ByteRover built-in provider requires a logged-in ByteRover account (/login or brv login).

​
Upgrade from local to cloud

1

Authenticate

Run /login inside the REPL to authenticate via browser:
/login
2

Add a remote

Point your space to a remote on ByteRover cloud:
/vc remote add origin https://byterover.dev/<team>/<space>.git
Find the URL on the space’s page in the ByteRover Dashboard.
3

Push local context to cloud

Push your commits to the remote space. Use -u to set upstream tracking:
/vc push -u origin main
4

Pull on other machines

On any machine where you’re authenticated, clone the space:
/vc clone https://byterover.dev/<team>/<space>.git
After the initial clone, use /vc pull to sync subsequent changes from teammates.

​
When to use cloud

Use caseWhy
Team collaborationShare a space with teammates — everyone queries the same knowledge base
Multi-machine syncPush from your laptop, pull on a server or a new machine
BackupPersist your context tree outside the local repo
All local features — curate, query, version control, provider selection, hub, connectors — work without a cloud account and without an internet connection when using a third-party or local LLM provider. The ByteRover built-in provider requires a logged-in ByteRover account.

​
Next steps

Team Context Sync

Full walkthrough of the shared context workflow for teams

Local Context Tree

Understand the local knowledge store before pushing it to cloud

Git-Semantic VC

Full guide to branching, merging, and remote sync

CLI Reference

Complete flag reference for all commands