Most users only need brv webui. The commands below are for advanced users and automation. Run brv --help for the full, up-to-date reference.

Core Workflow

brv                  # Start interactive REPL
brv webui            # Open the ByteRover dashboard (primary UI)
brv status           # Show project and daemon status
brv curate           # Add context to knowledge storage
brv curate view      # View curate history
brv query            # Query context tree and knowledge
brv review pending   # List pending review operations
brv review approve   # Approve curate operations
brv review reject    # Reject curate operations

Sync (Legacy)

brv push             # Legacy — migrate or snapshot context to cloud
brv pull             # Legacy — restore context from cloud snapshot

Use brv vc push / brv vc pull for version-controlled sync going forward.

Version Control

brv vc init              # Initialize version control for context tree
brv vc status            # Show version control status
brv vc add               # Stage files for the next commit
brv vc commit            # Save staged changes as a commit
brv vc log               # Show commit history
brv vc branch            # List, create, or delete branches
brv vc checkout          # Switch branches
brv vc merge             # Merge a branch into the current branch
brv vc clone             # Clone a ByteRover space repository
brv vc push              # Push commits to ByteRover cloud
brv vc pull              # Pull commits from ByteRover cloud
brv vc fetch             # Fetch refs from ByteRover cloud
brv vc remote            # Show current remote origin
brv vc remote add        # Add a named remote
brv vc remote set-url    # Update a remote URL
brv vc config            # Get or set commit author
brv vc reset             # Unstage files or undo commits

Providers & Models

brv providers list       # List available LLM providers
brv providers connect    # Connect to an LLM provider
brv providers switch     # Switch active provider
brv providers disconnect # Disconnect a provider
brv model list           # List available models
brv model switch         # Switch active model

Hub & Connectors

brv hub list             # List available hub packages
brv hub install          # Install a hub package
brv hub registry add     # Add a custom registry
brv hub registry list    # List registries
brv hub registry remove  # Remove a registry
brv connectors list      # List connectors
brv connectors install   # Install a connector

Spaces (Deprecated)

brv space list       # Deprecated — use web dashboard
brv space switch     # Deprecated — use brv vc clone

Settings

brv ships with operational defaults that suit most users. The brv settings command group lets you inspect and override these values.

brv settings                    # List all settings with current and default values
brv settings list               # Alias for `brv settings`
brv settings get <key>          # Show current and default for one key
brv settings set <key> <value>  # Update one key (restart required)
brv settings reset <key>        # Restore one key to its default (restart required)

Available keys:

Raise llm.iterationBudgetMs when a single brv curate or brv query on a slow local LLM (Ollama on CPU, heavy quantization, cold model load) routinely hits the default 10-minute cap on legitimate work. Lower it on cloud providers when you want a stuck task to surface as an error faster instead of waiting out the full budget. The cap is enforced per task, not per request.

llm.requestTimeoutMs bounds one HTTP request to the LLM. A frozen Ollama or LM Studio connection aborts at this boundary and the retry layer treats it as a transient error rather than wasting the full iteration budget. The setting must satisfy llm.requestTimeoutMs <= llm.iterationBudgetMs; the daemon rejects writes that violate the rule and falls back to defaults for both keys when the file violates it at startup. Suggested presets:

Settings persist in settings.json under the brv global data directory:

• Linux: $XDG_DATA_HOME/brv/settings.json (defaults to ~/.local/share/brv/settings.json)
• macOS: ~/Library/Application Support/brv/settings.json
• Windows: %LOCALAPPDATA%/brv/settings.json

Set the BRV_DATA_DIR environment variable to override the directory.

Changes apply after brv restart. The daemon reads the file once at startup and does not observe file changes during runtime. This keeps every running agent on the same configuration for the lifetime of the daemon.

Example session:

$ brv settings list
KEY                                       CURRENT  DEFAULT  RESTART?
agentPool.maxSize                         10       10       yes
agentPool.maxConcurrentTasksPerProject    5        5        yes
taskHistory.maxEntries                    1000     1000     yes

$ brv settings set agentPool.maxSize 20
Setting saved. Run `brv restart` to apply.

$ brv settings get agentPool.maxSize
20  (default: 10)

Every command supports --format json for scripting. Validation errors (unknown key, value out of range) exit with code 1 and a message naming the key.

Other

brv mcp              # Start MCP server
brv login            # Authenticate to ByteRover
brv logout           # Disconnect and clear credentials
brv locations        # List registered projects
brv restart          # Restart daemon
brv debug            # Debug mode

Run brv --help for the full command reference.

ByteRover CLI supports 20 LLM providers out of the box. Connect and switch providers from the dashboard, or use brv providers connect / brv providers switch.