honcho

Configure Honcho cross-session memory, peer profiles, and dialectic reasoning for Hermes agents.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/azaanaliraza/operarius --skill honcho-azaanaliraza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: honcho
Source: https://github.com/azaanaliraza/operarius/tree/main/src-tauri/bin/hermes/optional-skills/autonomous-ai-agents/honcho
Command: npx skills add https://github.com/azaanaliraza/operarius --skill honcho-azaanaliraza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires honcho-ai.

What problem does it solve? AI agents lose all knowledge of the user between conversations, forcing repetitive re-explanation and preventing personalized, continuous assistance. This Skill configures Honcho memory for Hermes so user preferences, facts, and session context persist across conversations and across multiple agent profiles. ## Core Features & Use Cases - Cross-Session User Modeling: Honcho builds a persistent representation of each user, injecting session summaries, user representations, and peer cards into the system prompt automatically. - Multi-Profile Peer Isolation: Each Hermes profile gets its own AI peer while sharing a unified view of the user, so specialized agents develop independent identities. - Tunable Dialectic Reasoning: Three orthogonal knobs (cadence, depth, level) control how often, how many rounds, and how intensely Honcho's reasoning engine synthesizes answers. - Five Memory Tools: honcho_profile, honcho_search, honcho_context, honcho_reasoning, and honcho_conclude give the agent bidirectional read/write access to user and AI peer memory. - Use Case: A developer runs separate "coder" and "writer" Hermes profiles; both remember the user's preferences, while each maintains its own self-knowledge and observation settings. ## Quick Start Set up Honcho memory for my Hermes agent by running the interactive setup wizard and verifying the connection with the status command.

Frequently Asked Questions about honcho

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

FAQPage Schema
How do I set up Honcho memory with Hermes?▼

Run hermes honcho setup and choose cloud (paste an API key from app.honcho.dev) or local (enter a self-hosted base URL). Verify the connection and resolved configuration with hermes honcho status.

How do I give each Hermes profile its own Honcho peer?▼

Create profiles with hermes profile create <name> --clone, which creates a host block, sets the aiPeer to the profile name, and inherits shared settings. For existing profiles, run hermes honcho sync to backfill host blocks.

What is the difference between hybrid, context, and tools recall modes?▼

Hybrid auto-injects context and exposes the five Honcho tools. Context mode auto-injects only, hiding tools to minimize token cost. Tools mode disables auto-injection so the agent controls all memory access explicitly.

Why is Honcho memory not persisting across sessions?▼

Check hermes honcho status and confirm saveMessages is true and writeFrequency is not set to session, which only writes on exit. Also verify memory.provider is set to honcho in the Hermes config.

How do I control Honcho dialectic reasoning cost and depth?▼

Tune three independent settings: dialecticCadence controls how often calls fire, dialecticDepth sets reasoning rounds per query (1-3), and dialecticReasoningLevel sets intensity from minimal to max. Higher values increase token cost on Honcho's backend.

When should I use honcho_reasoning versus honcho_search?▼

Use honcho_search for fast retrieval of specific past facts as raw excerpts with no LLM call. Use honcho_reasoning only when you need a synthesized answer about user patterns or goals, since it triggers an LLM call on Honcho's backend.