Overview

Documentation Index

Fetch the complete documentation index at: https://docs.byterover.dev/llms.txt

Use this file to discover all available pages before exploring further.

​

Connect a provider

• TUI
• CLI

1

Open the provider selector

/providers

ByteRover lists all providers with a short description of each (what its models are known for) and status indicators — (Current) for the active provider, [Connected] for previously connected ones.

2

Select and connect

Select an unconnected provider. Providers that support OAuth (currently OpenAI) will present a choice — “Sign in with OAuth” to authenticate via your browser, or “API Key” to enter a key manually. Other providers prompt for an API key directly. ByteRover validates credentials before saving. After connecting, a model selector opens automatically.Picking ByteRover while signed in to one or more paid teams shows a billing-team picker as part of the connect flow. The team you choose is remembered for the current project; switching teams later is non-destructive. See Pick a billing team below.

1

List available providers

brv providers list

2

Connect with your API key or OAuth

brv providers connect <provider-id> --api-key <your-key>

Optionally set the active model in the same step:

brv providers connect anthropic --api-key sk-ant-... --model claude-sonnet-4-5-20250929

For providers that support OAuth (currently OpenAI), you can authenticate via your browser instead:

brv providers connect openai --oauth

To switch back to the ByteRover built-in (requires brv login first):

brv login                          # opens your browser for OAuth
# or on CI / SSH:
# brv login --api-key <your-api-key>
brv providers connect byterover

# Pin this project to a paid team (byterover provider only):
brv providers connect byterover --team acme

--team accepts a team name or slug. It is only supported for the byterover provider; passing it elsewhere fails with a clear error. See Pick a billing team below.If authentication or connection fails, the CLI displays the specific error — follow the instructions in the message to resolve it.

​

Select a model

• TUI
• CLI

1

Open the model browser

/model

Models are grouped by provider, with pricing and context window size shown when available.

2

Select a model

Use arrow keys to browse and press Enter to select. You can also type to filter models by name or provider.

1

List available models

List models from all connected providers:

brv model list

Filter to a specific provider:

brv model list --provider openrouter

2

Switch to a model

Switch to a model on the active provider:

brv model switch <model-id>

Switch a model on a specific provider without changing the active provider:

brv model switch gpt-4.1 --provider openai

Show the currently active model:

brv model

​

Switch providers

/providers

brv providers switch <provider-id>

brv providers

​

Pick a billing team

• TUI / web UI: as a step in the ByteRover provider-connect flow, after sign-in, only if you have at least one paid team.
• CLI: pass --team <name> to brv providers connect byterover. The flag accepts a team name or slug and is only supported for the byterover provider.

ByteRover usage on this project will be billed to <team>.

• REPL header: Billing: <team> (<remaining> credits, <tier>) for paid teams, or Billing: Personal free credits (<remaining> / <total>) for the free tier.
• Web UI: a <N> cr pill next to each team row in the picker and in the page header (e.g. 12.4k cr, 50k cr). One decimal of precision so 12.4k and 12.9k stay distinguishable.

• CLI — brv curate and brv query fail and a message that names every other paid team you could switch to. For free-tier accounts, the message tells you to upgrade to a paid team.
• Web UI — the provider picker shows an “exhausted” alert with a Top up button. The button opens your team’s billing settings in a new tab. You can also pick another team or switch to a bring-your-own-key provider directly from the alert.

​

Disconnect a provider

• TUI
• CLI

1

Open the provider selector

/providers

2

Select a connected provider

Select a connected provider to open the actions menu.

3

Select Disconnect

Choose Disconnect to remove the stored API key and disconnect the provider.

brv providers disconnect <provider-id>

​

Local LLM setup

• TUI
• CLI

1

Serve your model

Make sure your local LLM server is running before connecting.

2

Connect the provider

Run /providers and select OpenAI Compatible. ByteRover prompts you to enter the base URL of your endpoint:

/providers

Enter your base URL (e.g., http://localhost:11434/v1 for Ollama). An API key prompt follows — leave it blank if your server doesn’t require one.

3

Select your model

/model

1

Serve your model

Make sure your local server is running before connecting.

2

Connect the provider

Pass your base URL with --base-url. API key is optional:

brv providers connect openai-compatible --base-url http://localhost:11434/v1

With an API key (e.g., for LM Studio with auth enabled):

brv providers connect openai-compatible --base-url http://localhost:1234/v1 --api-key <your-key>

3

Switch to your model

brv model switch llama3

​

Supported providers

​

Recommended LLM list

​

Environment variable auto-detection

​

Hot-swap

• Provider changed — a new session is created. In-memory conversation history is cleared (history formats are incompatible across providers).
• Model only changed — the session ID is reused, but in-memory conversation history is still lost on the new session manager.

​

Credential storage

​

Next steps