Skip to main content
OpenClaw is a general AI agent that can perform actions on behalf of a user. The Honcho plugin gives OpenClaw memory across every channel — WhatsApp, Telegram, Discord, Slack, and more.
Honcho can run entirely locally with OpenClaw — no external API required. Keep your data on your machine while getting full memory capabilities across all channels. See the self-hosting guide to get started.

Get Your API Key

Create a Honcho API key from app.honcho.dev, then add it to your OpenClaw env file:
echo "HONCHO_API_KEY=hc_..." >> ~/.openclaw/.env

Install the Plugin

The honcho-setup skill on ClawHub handles installation, migration, and workspace setup interactively:
clawhub install honcho-setup
Then run the skill from a chat session. It will walk you through plugin installation, legacy memory migration, and workspace doc setup.

Option B: Manual Install

Install the plugin using the OpenClaw plugin system. Do not install @honcho-ai/sdk directly or use npm install in the workspace.
openclaw plugins install @honcho-ai/openclaw-honcho
Then enable it:
openclaw plugins enable openclaw-honcho
If the gateway logs show Cannot find module '@honcho-ai/sdk', install the plugin’s dependencies manually:
cd ~/.openclaw/extensions/openclaw-honcho && npm install
Restart the gateway after installing:
openclaw gateway restart

Migrating Legacy Memory

If you have existing workspace memory files (USER.md, MEMORY.md, IDENTITY.md, memory/, canvas/, etc.), these can be migrated to Honcho. The recommended path is the honcho-setup ClawHub skill, which handles this interactively.
Commit any existing memory files to version control before migrating.

Legacy files

User/owner files (content describes the user):
  • USER.md, IDENTITY.md, MEMORY.md
  • All files in memory/ and canvas/ directories
Agent/self files (content describes the agent):
  • SOUL.md, AGENTS.md, TOOLS.md, BOOTSTRAP.md, HEARTBEAT.md

Upload to Honcho

Files are uploaded to Honcho via the messages upload endpoint. User/owner files are uploaded through the owner peer, and agent/self files through the openclaw peer. The honcho-setup skill automates this using session.uploadFile().

Archive originals

After uploading:
  1. Remove originals for legacy-only files: USER.md, MEMORY.md, IDENTITY.md, HEARTBEAT.md
  2. Keep originals for active workspace docs: AGENTS.md, TOOLS.md, SOUL.md, BOOTSTRAP.md
  3. Move directories (memory/, canvas/) into an archive/ directory

How It Works

Once installed, the plugin runs automatically:
  • Message Observation — After every AI turn, the conversation is persisted to Honcho. Both user and agent messages are observed, allowing Honcho to build and refine its models.
  • Tool-Based Context Access — The AI can query Honcho mid-conversation using tools like honcho_recall, honcho_search, and honcho_analyze to retrieve relevant context.
  • Dual Peer Model — Honcho maintains separate representations: one for the user (preferences, facts, communication style) and one for the agent (personality, learned behaviors).

AI Tools

Data Retrieval (fast, no LLM)

ToolDescription
honcho_sessionConversation history and summaries from the current session.
honcho_profileUser’s peer card — key facts (name, preferences, role).
honcho_searchSemantic search over stored observations.
honcho_contextFull user representation across all sessions.

Q&A (LLM-powered)

ToolDescription
honcho_recallSimple factual question — minimal reasoning.
honcho_analyzeComplex question requiring synthesis — medium reasoning.

CLI Commands

openclaw honcho status                          # Connection status
openclaw honcho ask <question>                  # Query Honcho about the user
openclaw honcho search <query> [-k N] [-d D]    # Semantic search (topK, maxDistance)

Configuration

Optional — the plugin works out of the box with HONCHO_API_KEY set.
KeyDefaultDescription
workspaceId"openclaw"Honcho workspace ID for memory isolation.
baseUrl"https://api.honcho.dev"API endpoint (for self-hosted instances).

Self-Hosted Honcho

Point the plugin to your local instance and follow the self-hosting guide to get started:
echo "HONCHO_BASE_URL=http://localhost:8000" >> ~/.openclaw/.env

Local File Search (QMD Integration)

The plugin automatically exposes OpenClaw’s memory_search and memory_get tools when a memory backend is configured, allowing both Honcho cloud memory and local file search together.

Setup

  1. Install QMD on your server
  2. Configure OpenClaw in ~/.openclaw/openclaw.json:
{
  "memory": {
    "backend": "qmd",
    "qmd": {
      "limits": {
        "timeoutMs": 120000
      }
    }
  }
}
  1. Set up QMD collections and restart:
qmd collection add ~/Documents/notes --name notes
qmd update
openclaw gateway restart

Available Tools

When QMD is configured, you get both Honcho and local file tools:
ToolSourceDescription
honcho_*HonchoCross-session memory, user modeling, dialectic reasoning
memory_searchQMDSearch local markdown files
memory_getQMDRetrieve file content

Next Steps