Skip to main content

​
Step 1: Push to remote

In the Console tab, sync your context tree to your remote space: 
/push
Push to Remote Your context is now available to your team and persists across sessions.

​
Step 2: Pull team context

When teammates push context to your shared space, use /pull in the Console tab: 
/pull
Pull Team Context Now you have access to your team’s collective knowledge. This is how ByteRover creates shared team memory.

​
Step 3: Complete workflow cycle

Now put it all 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 Context Tree to understand your codebase patterns:
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: 
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. Push to remote in the Console tab to share the new context with your team:
/push
  1. Pull team updates in the Console tab to get context that teammates have added:
/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.

​
Next steps

Curate Context

Learn best practices for adding context

Query Context

Master context retrieval techniques