honcho

Organize and persist user and AI memory across Hermes sessions with Honcho.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/AissenLiu/EasyHermes --skill honcho-aissenliu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: honcho
Source: https://github.com/AissenLiu/EasyHermes/tree/main/hermes-agent/optional-skills/autonomous-ai-agents/honcho
Command: npx skills add https://github.com/AissenLiu/EasyHermes --skill honcho-aissenliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Honcho memory enables cross-session user modeling and per-profile AI memory within Hermes, providing a unified user view while keeping each profile's data isolated.

Core Features & Use Cases

  • Cross-session memory across Hermes profiles with per-profile AI peers
  • Per-session and per-directory memory recall, observations, and session summaries
  • Configurable observation toggles and dialectic depth for personalized memory handling
  • Troubleshooting memory sync, onboarding cloud or self-hosted Honcho deployments

Quick Start

Run the Honcho setup to enable cross-session memory for your Hermes profile.

Frequently Asked Questions about honcho

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable cross-session memory recall across Hermes profiles?

Enable cross-session memory by running the Honcho setup to configure per-profile memory, which persists user and AI observations across Hermes sessions. This requires valid Honcho tokens and base prompts to function.

What is per-profile AI memory isolation in multi-profile setups?

Per-profile AI memory isolation keeps each profile's data separate while maintaining a unified user view. Honcho manages this by applying distinct memory configurations and peers to each Hermes profile session.

Can I use a self-hosted Honcho deployment with Hermes sessions?

Yes, you can use a self-hosted Honcho deployment with Hermes sessions. The skill supports both cloud and local deployments, requiring valid Honcho tokens and base prompts to establish the connection.

How do I tune dialectic depth for personalized memory handling?

Tune dialectic depth by configuring the observation toggles and dialectic settings within your Honcho memory configuration. This allows personalized memory handling for each AI peer across sessions.

Why does Honcho memory sync fail across Hermes sessions?

Honcho memory sync fails when valid Honcho tokens are missing or base prompts are incorrectly configured. Troubleshooting memory sync requires verifying your per-profile memory configuration and deployment access.