Skip to main content
The Configuration tab is where per-project plumbing lives — three panels stacked on one page:
  • Git identity — the user.name and user.email recorded on every commit in this project (the browser equivalent of brv vc config).
  • Remotes — the origin remote used by push, pull, and fetch (the browser equivalent of brv vc remote).
  • Connectors — the wire-up for coding agents like Claude Code, Cursor, and Codex (the browser equivalent of brv connectors).
Configuration tab

Git identity

Commits to your context tree need a name and email. Both are stored locally per project — the same values brv vc config user.name and brv vc config user.email would set. The panel renders one of three states:
  • Configured — name and email are shown inline as Name <email>. Click Edit to change either field.
  • Not set, signed in to ByteRover — your account name and email appear in a dashed-bordered row with a one-click Apply button that seeds the values from your account. Edit is still available if you want a different identity.
  • Not set, signed out — a “Set manually” button opens the empty form.
The form validates the email and only enables Save when both fields are non-empty and the email is valid.
Identity is optional for browsing the context tree, but brv vc commit and the Commit button in the Changes tab require it. If you commit before configuring identity, the Changes tab routes you back here.

Origin remote

Your local context tree can point at one ByteRover cloud remote, named origin. Push, pull, and fetch in the Changes tab and on the CLI all use this URL.
  • Add a remote — when version control is initialized but no remote is set, the panel header shows an Add remote button. The form accepts an HTTPS URL like https://byterover.dev/<team>/<space>.git and validates it before saving. Use Find in ByteRover to open the dashboard in a new tab and copy the URL.
  • Edit the URL — click Edit next to the existing origin row to replace the URL. The form previews “Replaces current URL <old>” so you can confirm before saving.
  • Delete the remote — click Delete next to the origin row. A confirmation dialog explains that push, pull, and fetch will be disabled until a new remote is set; click Remove remote to confirm or Cancel to back out.
If version control hasn’t been initialized for this project yet, the panel shows an Initialize version control button instead of the remote form.

Connectors

Wire your coding agents to ByteRover without editing their config files by hand. This is the browser equivalent of brv connectors — see the Agent Connectors overview for what each integration does.
  • See every supported agent and whether it’s already connected
  • Install a connector for any agent ByteRover detects on your machine
  • Remove a connector without hunting down the relevant config file

Next steps

Agent Connectors

Reference for supported agents.

Providers & Models

Connect LLM providers.

Changes

Stage, commit, push, and pull from the browser.

Git-Semantic VC

Full reference for the underlying commands.