Commands: local vs cloud
- TUI slash commands
- CLI commands
Commands available in the interactive REPL (
brv):| Works locally (no auth) | Requires cloud auth |
|---|---|
/status — show local project state | /login — authenticate with ByteRover |
/curate — add context to local knowledge tree | /logout — clear authentication |
/query — query local context tree | /push — sync local context to cloud |
/connectors — manage agent connectors | /pull — pull context from cloud |
/hub — browse and install skills & bundles | /space list — list team spaces |
/provider — connect and switch LLM providers | /space switch — switch active space |
/model — select a model | |
/reset — clear local context tree | |
/new — start a fresh session |
Upgrade from local to cloud
- TUI
- CLI
Switch to a space
Select a team space. ByteRover updates An interactive picker lists all spaces across your teams. Selecting one switches your project and pulls remote context in a single step.
.brv/config.json and automatically pulls any existing context from the remote space.
Push local context to cloud
Sync your 
.brv/context-tree/ to the remote space. Teammates can pull this immediately after.
When to use cloud
| Use case | Why |
|---|---|
| Team collaboration | Share a space with teammates — everyone queries the same knowledge base |
| Multi-machine sync | Push from your laptop, pull on a server or a new machine |
| Backup | Persist your context tree outside the local repo |
All local features — curate, query, provider selection, hub, connectors — work without a cloud account and without an internet connection when using a local LLM provider.
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
The Remote Space
How ByteRover processes and organizes context once it’s pushed to the cloud
CLI Reference
Complete flag reference for push, pull, and space commands