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.
This workflow covers bulk context extraction from your entire codebase. Your coding agent reads through your project and curates knowledge in multiple passes, automatically organizing everything into the context tree.
For onboarding individual files (1-3 documents), see Onboard Existing Context.
Prerequisites
- ByteRover CLI installed
- Project initialized (run
brv to start the REPL and initialize your project)
- A codebase with existing patterns, conventions, or documentation worth capturing
Step 1: Curate from Your Codebase
Via Coding Agent
Commands
Manual REPL
Copy this prompt and paste it into your coding agent’s chat (e.g., Cursor, Claude Code, etc.):> curate all important context from this codebase using brv curate; focus on:
1. Code Style and Quality
2. Styling and Design
3. Naming Conventions
4. Project Structure and Dependencies
ByteRover should intelligently organize into appropriate domains and topics
brv curate multiple times to capture the knowledge. ByteRover automatically organizes everything into the context tree. Curate from key documentation files using the -f flag:brv curate "Project architecture and conventions" -f README.md -f ARCHITECTURE.md -f CONTRIBUTING.md
brv curate "API patterns and authentication flow" -f src/api/routes.ts -f src/auth/middleware.ts
brv curate "Database models and schema" -f prisma/schema.prisma -f src/models/user.ts
brv curate "Testing patterns" -f tests/setup.ts -f tests/helpers.ts
brv curate "Frontend component conventions" -f src/components/Button.tsx -f src/styles/theme.ts
-d flag:ByteRover packs the folder into a structured representation and analyzes all supported files (code, config, docs, PDFs, Office files). See How Curation Works for full details on folder packing. Curate from key documentation files using the @ syntax:# In the REPL:
/curate "Project architecture and conventions" @README.md @ARCHITECTURE.md @CONTRIBUTING.md
# In the REPL:
/curate "API patterns and authentication flow" @src/api/routes.ts @src/auth/middleware.ts
/curate "Database models and schema" @prisma/schema.prisma @src/models/user.ts
/curate "Testing patterns" @tests/setup.ts @tests/helpers.ts
/curate "Frontend component conventions" @src/components/Button.tsx @src/styles/theme.ts
@ syntax with a trailing slash:ByteRover packs the folder into a structured representation and analyzes all supported files (code, config, docs, PDFs, Office files). See How Curation Works for full details on folder packing. Step 2: Review Changes
Verify what was added:
# In the REPL:
/vc status
Step 3: Query to Verify
Test that your context is retrievable.
Via Coding Agent
Commands
Manual REPL
Copy this prompt and paste it into your coding agent’s chat:> use brv query to retrieve context related to (your intention)
brv query with your query and return the relevant context. brv query "how is authentication implemented"
Run the /query command directly:# In the REPL:
/query how is authentication implemented
What Happened Behind the Scenes
-
Autonomous Analysis: ByteRover analyzed your codebase content and detected relevant domains (code_style, testing, structure, api, etc.) using semantic understanding.
-
Intelligent Organization: Content was organized hierarchically into the context tree at
.brv/context-tree/, with appropriate domain and topic structure.
-
Relation Mapping: ByteRover identified connections between related topics and created explicit
@domain/topic relations to build a navigable knowledge graph.
-
Duplicate Prevention: Before creating new topics, ByteRover searched for existing related knowledge to prevent duplication and update existing topics when appropriate.
-
Facts Extraction: ByteRover extracted structured facts from your content — categorized as
personal, project, preference, convention, team, environment, or other — and stored them in the ## Facts section of each knowledge file.
See How Curation Works for details.
Customizing Your Bootstrap
You can customize how ByteRover processes your codebase:
Focus on specific areas:
> curate context about testing patterns and conventions from this codebase using brv curate
> curate context from this codebase, break it into small focused pieces
> curate context from this codebase, summarize it before adding
Cloud Sync (Optional)
To share your bootstrapped context with teammates, stage, commit, and push:
brv vc add .
brv vc commit -m "bootstrap project context"
brv vc push
/vc add .
/vc commit -m "bootstrap project context"
/vc push
Next Steps
