Where Does ByteRover Store Memory and Settings?
ByteRover memory, context trees and settings on desktop OSes, from project .brv folders to daemon config.
Last updated
ByteRover keeps project memory inside the project as a .brv folder with a context tree of markdown files. That layout is git friendly and portable across machines. Daemon settings and provider configs live separately per OS.
The brv binary resolves from PATH, ~/.brv-cli/bin or npm global installs. Hermes integrations add ~/.hermes config on top. For most issues, check the project .brv first and global config second.
Where ByteRover stores this, by platform
%USERPROFILE%\Documents\GitHub\[Project]\.brv\context-tree
Holds context-tree markdown, swarm config and review state. Commit it to share memory with the team. Daemon binary often sits in ~/.brv-cli/bin or /usr/local/bin.
~/projects/[Project]/.brv/context-tree
Same project relative layout on every OS. Global Hermes config lives at ~/.hermes/config with BRV_API_KEY in ~/.hermes/.env when used.
~/projects/[Project]/.brv/context-tree
brv swarm status reports provider health. Swarm YAML sits at .brv/swarm/config.yaml inside the project when Memory Swarm is enabled.
Frequently asked questions
How do I back up ByteRover memory?
Copy the project .brv folder with the daemon stopped, or push and pull through cloud sync. The context tree is markdown, so git carries it cleanly. Review pending curations before sharing.
Why does my agent not see ByteRover memory?
Run brv locations to list registered projects, then brv in the project root. The REPL picks up .brv/context-tree automatically. Check connectors when agents miss memory.
Notice an outdated path? Let us know.