Skip to main content
This page documents ByteRover CLI v2.6.0 and earlier. The brv push, brv pull, and brv space switch commands described here have been deprecated in v3.0.0. For the current workflow, see Getting Started which uses Git-Semantic version control (brv vc) for all sync operations.
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):
* 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:
2

Switch to a space

Select a team space. ByteRover updates .brv/config.json and automatically pulls any existing context from the remote space.
An interactive picker lists all spaces across your teams. Selecting one switches your project and pulls remote context in a single step.Space switch interactive picker
3

Push local context to cloud

Sync your .brv/context-tree/ to the remote space. Teammates can pull this immediately after.
Push syncing context to cloud
4

Pull on other machines

On any machine where you’re authenticated, run /space switch to select the same space — it automatically pulls remote context. After the initial switch, use /pull to sync subsequent changes from teammates.

​
When to use cloud

All local features — curate, query, 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.