honcho

Configure Honcho cross-session memory for consistent user modeling across profiles.

19|4|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/carterwayneskhizeine/hermes-agent-windows-R --skill honcho-carterwayneskhizeine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: honcho
Source: https://github.com/carterwayneskhizeine/hermes-agent-windows-R/tree/main/optional-skills/autonomous-ai-agents/honcho
Command: npx skills add https://github.com/carterwayneskhizeine/hermes-agent-windows-R --skill honcho-carterwayneskhizeine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires honcho-ai.

What problem does it solve?

Honcho Memory for Hermes solves the problem of making AI remember who the user is across sessions while keeping multi-profile peers isolated yet consistent, so context stays coherent without relying on full chat history replay.

Core Features & Use Cases

  • Cross-session user modeling: Builds a unified user representation that persists across runs and injects it into Hermes prompts.
  • Multi-profile peer isolation: Gives each Hermes profile its own AI peer identity while sharing a common workspace and user view.
  • Controlled prompting and context budget enforcement: Supports cold/warm prompt strategies, recall modes (hybrid/context/tools), and trims injected memory to stay within token budgets.
  • Observation, recall, and dialectic tuning: Configures what each peer observes and how often/how deeply dialectic reasoning runs, enabling troubleshooting and performance optimization.

Quick Start

Run the Honcho setup wizard in your Hermes environment, then use the status command to verify resolved config, connection, and peer details.

Frequently Asked Questions about honcho

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

FAQPage Schema
How do I maintain cross-session memory for user modeling across multiple profiles?

Cross-session memory maintains a unified user representation across runs by configuring isolated AI peer identities that share a common workspace, injecting persistent context into prompts without full chat history replay. It applies multi-profile peer isolation to keep user modeling consistent yet separated.

How do I set up context budgeting to prevent injected memory from exceeding token limits?

Context budgeting trims injected memory representations to stay within specified token caps by enforcing session-summary and representation injection rules. You configure optional context token caps during setup to control how much memory the system injects into prompts.

Does Honcho work with self-hosted setups for multi-profile peer isolation?

Honcho works with both cloud and self-hosted setups for multi-profile peer isolation. You define the host identity model by setting user and AI peer identities, then apply observation and recall configuration to keep each profile isolated within a shared workspace.

What is dialectic reasoning tuning and when do I need it for troubleshooting memory recall?

Dialectic reasoning tuning configures how often and how deeply the system processes reasoning to build user representations. You need it when troubleshooting recall performance or optimizing how observations update the persistent memory model across active sessions.

How do I configure recall modes and observation toggles for cross-session memory?

Recall modes and observation toggles are configured by selecting hybrid, context, or tools recall strategies and defining what each AI peer observes. You apply cold or warm prompt strategies alongside these settings to control how memory representations are retrieved and injected.

Why does my cross-session memory lose user context between different profiles?

Cross-session memory loses context when peer isolation separates AI identities without sharing a common user view, or when observation toggles are disabled. Configuring a unified host identity model with shared workspace settings ensures consistent user representation across all isolated profiles.