Teknium
5d278aa31d
Config architecture: - Add save_config(values, hermes_home) to MemoryProvider ABC - Honcho: writes to $HERMES_HOME/honcho.json (SDK native) - Mem0: writes to $HERMES_HOME/mem0.json - Hindsight: writes to $HERMES_HOME/hindsight/config.json - Holographic: writes to config.yaml under plugins.hermes-memory-store - OpenViking/RetainDB/ByteRover: env-var only (default no-op) Setup wizard (hermes memory setup): - Now calls provider.save_config() for non-secret config - Secrets still go to .env via env vars - Only memory.provider activation key goes to config.yaml Documentation: - README.md for each of the 7 providers in plugins/memory/<name>/ - Requirements, setup (wizard + manual), config reference, tools table - Consistent format across all providers The contract for new memory plugins: - get_config_schema() declares all fields (REQUIRED) - save_config() writes native config (REQUIRED if not env-var-only) - Secrets use env_var field in schema, written to .env by wizard - README.md in the plugin directory
Hindsight Memory Provider
Long-term memory with knowledge graph, entity resolution, and multi-strategy retrieval. Supports cloud and local modes.
Requirements
- Cloud:
pip install hindsight-client+ API key from app.hindsight.vectorize.io - Local:
pip install hindsight+ LLM API key for embeddings
Setup
hermes memory setup # select "hindsight"
Or manually:
hermes config set memory.provider hindsight
echo "HINDSIGHT_API_KEY=your-key" >> ~/.hermes/.env
Config
Config file: $HERMES_HOME/hindsight/config.json (or ~/.hindsight/config.json legacy)
| Key | Default | Description |
|---|---|---|
mode |
cloud |
cloud or local |
bank_id |
hermes |
Memory bank identifier |
budget |
mid |
Recall thoroughness: low/mid/high |
Tools
| Tool | Description |
|---|---|
hindsight_retain |
Store information with auto entity extraction |
hindsight_recall |
Multi-strategy search (semantic + entity graph) |
hindsight_reflect |
Cross-memory synthesis (LLM-powered) |