Overview

Browser-based UI for ByteRover, served by your local daemon on localhost

Why a web UI?

Some things are just faster in a browser — reading long context files, scanning diffs, kicking off a task and walking away. The web UI gives you a visual way to do everything ByteRover already does, without replacing the CLI or TUI. It runs on your own machine, served by the local daemon, so nothing leaves your laptop unless you explicitly push.

The header also shows a compact ByteRover credits pill (e.g. 12.4k cr) when the built-in provider is active — see Providers & Models.

What you get

• Projects — Switch between projects from the header.

• Tasks — Run curate and query tasks visually.

• Contexts — Browse and edit your project's context tree.

• Changes — Review and commit changes to your context tree.

• Configuration — Manage git identity, the origin remote, and agent connectors.

• Providers & Models — Connect LLM providers and pick a model.

How it fits with CLI and TUI

The CLI, TUI, and web UI are three ways to drive the same ByteRover. Pick whichever matches the moment.

Client	Best for
CLI (brv query, brv curate, …)	Agent-driven calls and one-shot commands
TUI (brv)	Keyboard-first interactive sessions in the terminal
Web UI (brv webui)	Visual authoring, diff review, identity and remote setup, long-running tasks

Local-first

• Runs on your machine at http://localhost:<port> — not exposed to the network
• Context, tasks, and history come straight from your local .brv/ directory
• Pushing to the remote space is always an explicit action

Next steps

• Getting Started — Launch the web UI.

• Troubleshooting — Fix common issues.