Teknium e402afa783 fix(config): recognize runtime-read selection and plugin-declared keys in config get/set ...

`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.

2026-10-28 13:09:00 -07:00

..

byterover

fix(config): recognize runtime-read selection and plugin-declared keys in config get/set

2026-10-28 13:09:00 -07:00

retaindb

fix(config): recognize runtime-read selection and plugin-declared keys in config get/set

2026-10-28 13:09:00 -07:00

__init__.py

feat(plugins): register_hook(..., hold_stream=True) for transform_llm_output

2026-10-25 06:18:48 -07:00

config_schema.py

fix: plugin host review findings (async ctx, caller session, restarts, per-profile dashboard)

2026-10-03 10:15:11 -07:00

query_rewrite.py

…