`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.
11 lines
351 B
YAML
11 lines
351 B
YAML
name: byterover
|
|
version: 1.0.0
|
|
description: "ByteRover — persistent knowledge tree with tiered retrieval via the brv CLI."
|
|
external_dependencies:
|
|
- name: brv
|
|
install: "curl -fsSL https://byterover.dev/install.sh | sh"
|
|
check: "brv --version"
|
|
config_keys:
|
|
- memory.byterover
|
|
- memory.provider_config # legacy block name early docs used
|