honcho

Manage cross-session memory for Hermes profiles with shared workspace and CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Honcho memory for Hermes solves the challenge of maintaining user and profile context across sessions by providing per-profile AI peers within a shared workspace, enabling consistent memory, recall, and dialectic management.

Core Features & Use Cases

  • Cross-session memory with Honcho integration for Hermes, including session summaries, user representation, and AI peer cards.
  • Per-profile memory with shared workspace so multiple Hermes profiles can coexist and reuse a common memory context.
  • Support for recall modes (hybrid, context, tools) and configurable observation and dialectic settings to balance privacy, cost, and depth.
  • CLI and in-app tooling to manage Honcho peers, sync profiles, and adjust memory behavior for production or development environments.

Quick Start

Install Honcho for Hermes and enable memory per profile using the interactive setup.

Frequently Asked Questions about honcho

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

FAQPage Schema
How do I manage cross-session memory for multiple AI profiles?

Cross-session memory management for multiple AI profiles is handled by applying per-profile host blocks in a configuration file, allowing each profile to maintain its own AI peer within a shared workspace context.

How does cross-session memory recall work across different profiles?

Cross-session memory recall works by integrating shared workspace context with configurable recall modes like hybrid, context, and tools, enabling each profile to access persistent session summaries and user representations.

Can I balance privacy and memory depth when configuring AI peer sessions?

Yes, you can balance privacy and memory depth by adjusting configurable observation and dialectic settings, which directly control how the AI peer processes and retains session context.

Do I need a CLI to synchronize memory and manage profiles?

A CLI is required to manage Honcho peers, synchronize profiles, and adjust memory behavior across production or development environments, providing an interactive setup for per-profile memory configuration.

What is the best way to maintain user context across separate AI sessions?

The best way to maintain user context across separate AI sessions is by using a memory management system that provides session persistence, user representation, and AI peer cards within a common workspace.