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
Honcho Memory Provider
AI-native cross-session user modeling with dialectic Q&A, semantic search, peer cards, and persistent conclusions.
Requirements
pip install honcho-ai- Honcho API key from app.honcho.dev
Setup
hermes memory setup # select "honcho"
Or manually:
hermes config set memory.provider honcho
echo "HONCHO_API_KEY=your-key" >> ~/.hermes/.env
Config
Config file: $HERMES_HOME/honcho.json (or ~/.honcho/config.json legacy)
Existing Honcho users: your config and data are preserved. Just set memory.provider: honcho.
Tools
| Tool | Description |
|---|---|
honcho_profile |
User's peer card — key facts, no LLM |
honcho_search |
Semantic search over stored context |
honcho_context |
LLM-synthesized answer from memory |
honcho_conclude |
Write a fact about the user to memory |