ByteRover Docs

Appearance

Team Context Sync ​

Collaborate with your team by syncing context to the cloud using Git-Semantic version control

Team sync uses Git-Semantic version control (brv vc) to push and pull commits between your local context tree and ByteRover cloud. Your core workflow (curate and query) works fully offline — cloud sync is optional and designed for team collaboration.

NOTE

Cloud sync requires authentication. Run /login or brv login to connect your cloud account. See Local vs Cloud for full setup instructions.

When You Need Push/Pull ​

Use caseWhy
Team collaborationShare curated knowledge so teammates query the same context
Multi-machine syncPush from your laptop, pull on a server or CI environment
BackupPersist your context tree outside the local .brv/ directory

If you are working solo on a single machine, you do not need push or pull. Everything curated locally is immediately queryable.

Setup: Connect to a remote space ​

Before pushing or pulling, connect your local space to a remote:

New space (local to cloud)

Step 1: Initialize version control ​

bash
brv vc init
brv vc config user.name "Your Name"
brv vc config user.email "you@example.com"

Step 2: Add a remote ​

bash
brv vc remote add origin https://byterover.dev/<team>/<space>.git

Find the URL on the space's page in the ByteRover Dashboard.

Existing space (cloud to local)

Clone a space that already exists on ByteRover cloud:

CLI

bash
brv vc clone https://byterover.dev/<team>/<space>.git
brv vc config user.name "Your Name"
brv vc config user.email "you@example.com"

TUI

/vc clone https://byterover.dev/<team>/<space>.git
/vc config user.name "Your Name"
/vc config user.email "you@example.com"

Or omit the URL to browse your team's spaces with an interactive picker:

/vc clone

Cloning downloads the full context tree with its complete commit history. The remote is already configured.

Step 1: Stage and commit ​

After curating context, stage your changes and create a commit:

CLI

bash
brv vc add .
brv vc commit -m "add rate limiting context"

TUI

/vc add .
/vc commit -m "add rate limiting context"

Step 2: Push to remote ​

Push your commits to ByteRover cloud:

CLI

bash
brv vc push

On the first push, set upstream tracking:

bash
brv vc push -u origin main

TUI

/vc push

On the first push, set upstream tracking:

/vc push -u origin main

Your context is now available to your team.

Step 3: Pull team context ​

When teammates push context, pull their changes into your local context tree:

CLI

bash
brv vc pull

TUI

/vc pull

Now you have access to your team's collective knowledge.

Complete workflow cycle ​

The local-first flow is: curate locally → commit → (optionally) push/pull for teams. Here is how it all fits together.

Prompt your coding agent to implement a task, mentioning ByteRover:

> Add a rate limiter to the API endpoints. Use ByteRover to check existing patterns first.

Your coding agent will:

  1. Query existing context in the local context tree to understand your codebase patterns:
bash
brv query "How are API endpoints structured? Are there any rate limiting patterns?"

  1. Implement the task using the retrieved context as guidance.

  2. Curate new context to capture what it learned:

bash
brv curate "Rate limiting uses sliding window algorithm at 100 req/min per user. Implemented in rateLimiter.ts middleware." -f src/middleware/rateLimiter.ts
  1. Stage and commit the new context:
bash
brv vc add .
brv vc commit -m "add rate limiting patterns"

At this point your new context is committed locally and queryable. The following steps are optional and only needed for team collaboration:

  1. (Optional) Push to remote to share the new context with your team:
bash
brv vc push
  1. (Optional) Pull team updates to get context that teammates have added:
bash
brv vc pull

This creates a feedback loop where your coding agent learns from past decisions and contributes new knowledge back to your team's shared memory.

Handling conflicts ​

If teammates have pushed changes that conflict with yours, brv vc pull will report a merge conflict. Resolve it using the merge workflow:

bash
# Edit the conflicting files to resolve markers (<<<<<<<, =======, >>>>>>>)

# Stage the resolved files and complete the merge
brv vc add .
brv vc merge --continue -m "resolve merge conflicts"

For more details, see Branching & Merging.

Next steps ​

  • Local vs Cloud — Full breakdown of local and cloud commands with setup instructions

  • Remote Sync — Full push, pull, fetch, and remote management reference

  • Curate Context — Learn best practices for adding context