`hermes config get browser.cloud_provider` / `browser.use_gateway` warned "not a recognized config key" although the runtime selects the browser provider from them. The validator only walks DEFAULT_CONFIG, and provider selections stay unseeded on purpose (a stored key is the explicit pick), as do core-section keys plugins read. - tools.tool_backend_helpers.selection_config_keys(): the keys read_selection() honours (<category>.use_gateway, browser.cloud_provider, stt/tts/image_gen/video_gen provider keys, web.backend/search_backend/extract_backend). - plugin.yaml / dashboard manifest.json `config_keys`: a plugin names the core-section paths it reads; declared for retaindb, byterover, computer_use/cua, kanban dashboard. - hermes_cli/config_runtime_keys.py consults both before the DEFAULT_CONFIG walk. Found on Hermes Cloud staging.
ByteRover Memory Provider
Persistent memory via the brv CLI — hierarchical knowledge tree with tiered retrieval (fuzzy text → LLM-driven search).
Requirements
Install the ByteRover CLI:
curl -fsSL https://byterover.dev/install.sh | sh
# or
npm install -g byterover-cli
Setup
hermes memory setup # select "byterover"
Or manually:
hermes config set memory.provider byterover
# Optional cloud sync:
echo "BRV_API_KEY=your-key" >> ~/.hermes/.env
Config
| Env Var | Required | Description |
|---|---|---|
BRV_API_KEY |
No | Cloud sync key (optional, local-first by default) |
Working directory: $HERMES_HOME/byterover/ (profile-scoped).
Tools
| Tool | Description |
|---|---|
brv_query |
Search the knowledge tree |
brv_curate |
Store facts, decisions, patterns |
brv_status |
CLI version, tree stats, sync state |