Summary

The Honcho memory integration can generate workspace/peer IDs containing dots, e.g. hermes.asher, but Honcho validates IDs with:

^[a-zA-Z0-9_-]+$

This causes peer/session registration failures after the Honcho backend URL is configured correctly.

Environment

• Hermes Agent checkout: NousResearch/hermes-agent
• Memory provider: Honcho plugin
• Honcho backend: external HTTP(S) service
• Profile/workspace shape observed: hermes.asher

Observed behavior

After fixing the Honcho baseUrl, hermes honcho status / session registration failed because the client attempted to use IDs like:

workspace_id = hermes.asher
ai_peer      = hermes.asher

Honcho rejected those IDs because dots are not allowed.

Expected behavior

Hermes should generate Honcho-safe IDs, or sanitize profile-derived IDs before using them as:

• workspace IDs
• AI peer IDs
• user peer IDs if applicable

Example:

hermes.asher -> hermes-asher

Proposed fix

Sanitize Honcho identifiers in the Honcho memory client before API calls, replacing characters outside [a-zA-Z0-9_-] with -.

Also add regression tests for profile-derived IDs containing dots.

Impact

Honcho memory integration appears broken for profiles or generated IDs containing dots, even when the Honcho backend itself is healthy and reachable.