honcho

Configure Honcho cross-session memory with peer isolation, dialectic reasoning, and context budgets.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill honcho-chensihakniroth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: honcho
Source: https://github.com/Chensihakniroth/ANAKOT-AGENT/tree/main/optional-skills/autonomous-ai-agents/honcho
Command: npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill honcho-chensihakniroth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires honcho-ai.

What problem does it solve? AI agents lose track of who the user is between conversations, forcing users to repeat context every session. This Skill configures Honcho memory for Anakot so user preferences, facts, and patterns persist across sessions while each agent profile maintains its own isolated peer identity. ## Core Features & Use Cases - Cross-Session User Modeling: Honcho builds a user representation from observed messages and injects session summaries, representations, and peer cards into the system prompt automatically. - Multi-Profile Peer Isolation: Each Anakot profile gets its own AI peer sharing one workspace, so agents develop independent views while seeing the same user model. - Tunable Dialectic Engine: Three orthogonal knobs (cadence, depth, reasoning level) control how often, how many rounds, and how hard Honcho's dialectic reasoning runs, plus five bidirectional tools for profile, search, context, reasoning, and conclusions. - Use Case: You run separate "coder" and "writer" agent profiles. Use this Skill to give each its own Honcho peer via anakot profile create coder --clone, tune dialecticDepth to 2 for the coder, and cap contextTokens so long sessions never blow up the prompt. ## Quick Start Set up Honcho memory for my Anakot agent and show me the connection status and peer configuration.

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 Anakot?▼

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

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

Create profiles with `anakot profile create <name> --clone`, which creates a host block, sets the AI peer to the profile name, and inherits the shared workspace. For existing profiles, run `anakot honcho sync` to backfill missing host blocks.

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

Hybrid (default) 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 `anakot honcho status` and verify `saveMessages` is true and `writeFrequency` is not set to `session`, which only writes on exit. Also confirm `memory.provider: honcho` is set in the Anakot config.

How do I reduce Honcho context injection size in long sessions?▼

Set the `contextTokens` budget, which trims the session summary first, then the representation, while preserving the peer card. You can also lower `dialecticDepth` or raise `dialecticCadence` to reduce backend calls.

When should I use honcho_reasoning versus honcho_search?▼

Use honcho_search for fast, no-LLM retrieval of specific past facts as raw excerpts. Use honcho_reasoning only when you need synthesized insight from Honcho's dialectic engine, since it triggers an LLM call at medium-to-high cost.