The Remote Space

The remote space stores and syncs your context tree — the essential knowledge you and your team need for agentic development. ByteRover manages and processes all context pushed to this space.

Push to the Remote Space

After reviewing your context tree locally with /status, stage, commit, and push to sync with the remote space:

/vc add .
/vc commit -m "update context tree"
/vc push

Pushing uploads your committed changes to ByteRover's cloud, including all scoring metadata, maturity tiers, and relations. This enables team-wide access to the same organized knowledge.

Pull Updates from Remote

Team members sync the organized context tree to their local environment:

/vc pull

This updates your local .brv/context-tree/ directory with the latest organized knowledge, scoring metadata, and any changes made by other team members.

What Gets Synced

Push and pull operate on your curated knowledge files only. System-generated files are excluded from sync — they are rebuilt locally on demand:

File	Synced	Reason
Knowledge files (*.md)	Yes	Core curated content
context.md overviews	Yes	Agent-authored domain/topic descriptions
_index.md summaries	No	Regenerated after each local curate
_manifest.json	No	Rebuilt from local tree state
_archived/*.stub.md	No	Local-only ghost cues
_archived/*.full.md	No	Local-only lossless archives

What's Coming

NOTE

The following features for the remote space are planned for an upcoming release:

• Deep version control — Git-like history tracking, branching, and rollback for your context tree
• Audit trails — Full attribution and change logging for every update
• Team review workflows — Pull-request-style reviews and approval processes for context changes
• Conflict resolution — Smart three-way merge when team members make concurrent edits