Files

Erosika 827ce602db fix(honcho): harden self-hosted setup paths

Self-hosted Honcho setup had four sharp edges:

- local/cloud URLs ending in /vN double-prefixed by the SDK (/v3/v3/... 404)
- authenticated local servers had no setup prompt for a JWT/bearer token
- profile-derived host keys could be dot-containing workspace IDs Honcho rejects
- memory-provider config files with API keys written world-readable per umask

This keeps existing behavior but makes those paths safer:

- strip a trailing /vN version segment from any configured baseUrl before SDK
  init (the SDK's route builders always prepend their own version prefix);
  auth-skipping stays loopback-only
- add an optional local JWT/bearer prompt in honcho setup, stored under
  hosts.<host>.apiKey
- derive new profile host keys with underscores, still reading legacy
  hermes.<profile> blocks
- write memory-provider config files atomically with 0600 via a shared
  utils.atomic_json_write(mode=) arg (honcho/hindsight/mem0/supermemory)
- skip honcho.json parsing in gateway cache-busting unless Honcho is the active
  memory provider; memoize by honcho.json mtime when active
- bust the gateway agent cache on memory.provider change
- add a hermes memory setup <provider> one-liner so fresh installs can configure
  a named provider without the picker (the per-provider hermes <provider>
  subcommand only registers once that provider is active)

Closes #20688, #29885, #26459, #30246, #33382, #32244.

Co-authored-by: BROCCOLO1D

2026-05-29 22:29:48 -07:00

__init__.py

fix(honcho): harden self-hosted setup paths

2026-05-29 22:29:48 -07:00

plugin.yaml

feat(memory): pluggable memory provider interface with profile isolation, review fixes, and honcho CLI restoration (#4623 )

2026-04-02 15:33:51 -07:00

README.md

feat(memory): pluggable memory provider interface with profile isolation, review fixes, and honcho CLI restoration (#4623 )

2026-04-02 15:33:51 -07:00

README.md

Mem0 Memory Provider

Server-side LLM fact extraction with semantic search, reranking, and automatic deduplication.

Requirements

pip install mem0ai
Mem0 API key from app.mem0.ai

Setup

hermes memory setup    # select "mem0"

Or manually:

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

Config

Config file: $HERMES_HOME/mem0.json

Key	Default	Description
`user_id`	`hermes-user`	User identifier on Mem0
`agent_id`	`hermes`	Agent identifier
`rerank`	`true`	Enable reranking for recall

Tools

Tool	Description
`mem0_profile`	All stored memories about the user
`mem0_search`	Semantic search with optional reranking
`mem0_conclude`	Store a fact verbatim (no LLM extraction)