ByteRover CLI
The brv CLI memory layer for coding agents: structured project context, git-like versioning and an MCP server
- 4,946 ★ on the repository
- Last commit
Extended access
Why this level
- The CLI reads and writes project files and executes code at the agent's request
- With cloud enabled, some data is sent to ByteRover servers
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/byterover-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI reads and writes project files and executes code at the agent's request
- With cloud enabled, some data is sent to ByteRover servers
This is third-party code. Review the repository files before installing.
What it does
ByteRover CLI gives the brv command an interactive REPL for accumulating project knowledge: architecture facts, decisions, references to specific files. Context is stored as a tree with git-like versioning: branches, commits, merges, push and pull. The tool works with more than 20 LLM providers and ships an MCP server through which any supported coding agent can read and add to this memory. It includes a web dashboard for browsing history and optional cloud sync across machines and teammates.
Who it is for. For developers who want a coding agent to remember project context across sessions and share it with a team.
Good fit when
- The agent should remember project decisions and agreements across sessions
- You need to share accumulated context with other team members
- You need a standalone MCP memory layer that several agents can connect to
Not a fit when
- In-session memory from the agent itself is already enough
- You do not want to run a separate daemon process and context store
Example request
Save to project context that auth uses JWT with a 24-hour tokenLimitations
Some features, such as cross-machine cloud sync, team spaces and the built-in hosted model, require the paid ByteRover Cloud; local use is free. The local REPL needs an API key for the chosen LLM provider.
How to disable. Remove the package with npm uninstall -g byterover-cli, or delete the binary installed by the install script, stopping the background daemon first with brv restart.
FAQ
Is ByteRover Cloud required?
No, everything works locally by default; the cloud adds sync and collaboration on top of local mode.
How does an agent access the saved context?
Through the built-in MCP server started with brv mcp, or directly through the REPL and the brv curate and brv query commands.
Discussion
No questions or reviews yet.
Related
CLI toolsLocal memory for agents: decisions from browser chats reach Claude Code, Cursor and Windsurf through MCP
BrainAPI turns text into a knowledge graph on your server and serves agents over MCP, REST and a console with fact-path answers
Memory for agents over MCP: five tools, one local SQLite file and layers modeled on human memory, no account
AgentDB keeps agent memory in an .rvf file and, with 41 MCP tools, recalls past solutions while learning from feedback
WebUI and CLI daemon for remote work with local agents over ACP: Claude Code, OpenCode, Gemini CLI and 20+ more.
LongMemory keeps project memory in local SQLite and serves it to an agent over MCP: decisions, task state, skills and a code graph
README in short
The README describes ByteRover CLI as an interactive REPL tool that gives coding agents structured project memory: the agent reads and writes files, executes code, and stores knowledge for future sessions through curate and query commands. It supports more than 20 LLM providers and over 20 coding agents, including Cursor, Claude Code, Windsurf and Cline. The author publishes results on the LoCoMo and LongMemEval-S long-term memory benchmarks. Elastic 2.0 licensed.