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

RetainDB Memory Provider

Cloud memory API with hybrid search (Vector + BM25 + Reranking) and 7 memory types.

Requirements

  • RetainDB account ($20/month) from retaindb.com
  • requests is part of Hermes's core dependencies; no separate SDK install is needed. For damaged dependencies, use hermes pm repair and restart Hermes.

Setup

hermes memory setup    # select "retaindb"

Or manually:

hermes config set memory.provider retaindb
echo "RETAINDB_API_KEY=your-key" >> ~/.hermes/.env

Config

All config via environment variables in .env:

Env Var Default Description
RETAINDB_API_KEY (required) API key
RETAINDB_BASE_URL https://api.retaindb.com API endpoint
RETAINDB_PROJECT auto (profile-scoped) Project identifier

Tools

Tool Description
retaindb_profile User's stable profile
retaindb_search Semantic search
retaindb_context Task-relevant context
retaindb_remember Store a fact with type + importance
retaindb_forget Delete a memory by ID