honcho

Configure Honcho memory for ZedClaw cross-session user modeling and isolated AI profiles.

4|Updated May 18, 2026
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill honcho-zardli1115
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: honcho
Source: https://github.com/ZardLi1115/zedclaw/tree/main/optional-skills/autonomous-ai-agents/honcho
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill honcho-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires honcho-ai.

What problem does it solve?

Honcho Memory helps ZedClaw maintain consistent, cross-session user modeling by isolating AI profiles while sharing a unified understanding of the user.

Core Features & Use Cases

  • Cross-session user modeling: Learns user preferences and interaction patterns over time so profiles stay consistent across runs.
  • Multi-profile peer isolation: Gives each ZedClaw profile its own AI peer identity while using shared workspace-backed context.
  • Observation + recall control: Tunes what each peer learns (observeMe/observeOthers) and how memory is accessed (hybrid/context/tools) to balance cost and quality.
  • Dialectic + context budget tuning: Enforces injection budgets and controls reasoning cadence/depth to reduce context bloat and unnecessary LLM calls.

Quick Start

Run the cloud setup wizard by telling your agent: “Configure Honcho for ZedClaw using the cloud option and then verify the connection with honcho status.”

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 profiles for user modeling?

Cross-session memory profiles are maintained by configuring Honcho to isolate AI peers while sharing a unified user context, ensuring consistent modeling across runs. You set up host blocks per profile and tune observation settings.

Can I isolate multiple AI profiles while sharing a single user context?

Yes, multi-profile peer isolation gives each profile its own AI peer identity while using shared workspace-backed context. This requires creating or syncing Honcho host blocks per profile to manage the isolated peer configurations.

What's the best way to stop context bloat when using cross-session memory?

To stop context bloat, apply dialectic and context budget tuning by enforcing injection budgets and controlling reasoning cadence and depth. Aligning these parameters ensures safe context injection and reduces unnecessary LLM calls.

How do I configure Honcho recall modes and observation toggles?

Configure Honcho recall modes by selecting hybrid, context, or tools options to balance cost and quality. Tune observation toggles like observeMe and observeOthers to control what each peer learns during cross-session interactions.

Does Honcho memory work with both cloud and self-hosted setups?

Honcho memory works with both cloud and self-hosted setups. You can run the cloud setup wizard to configure the connection, or manually sync host blocks for self-hosted deployments, then verify with honcho status.

Why is my Honcho memory not syncing or persisting across sessions?

Honcho memory syncing and persistence issues often stem from misconfigured host blocks or incorrect observation and recall settings. Troubleshoot by verifying your profile configurations and aligning cadence, depth, and level parameters.