AI-native memory with dialectic reasoning for OpenClaw. Uses Honcho's peer paradigm to build and maintain separate models of the user and the agent — enabling context-aware conversations that improve over time. No local infrastructure required.
This plugin uses OpenClaw's slot system (kind: "memory") to replace the built-in memory plugins (memory-core, memory-lancedb). During setup, existing memory files can be migrated to Honcho. Workspace docs (SOUL.md, AGENTS.md, BOOTSTRAP.md) can be updated manually to reference Honcho's tools instead of the old file-based system.
openclaw plugins install @honcho-ai/openclaw-honcho
openclaw honcho setup
openclaw gateway restartopenclaw honcho setup prompts for your Honcho API key, writes the config, and optionally uploads any legacy memory files to Honcho.
Alternative: ClawHub Skill
Use the honcho-setup skill to run migration interactively from within a chat session:
# 1. Install the skill
npx clawhub install honcho-setup
# 2. Restart OpenClaw to pick up the new skill
# 3. Install the plugin
openclaw plugins install @honcho-ai/openclaw-honcho
# 4. Restart the gateway
openclaw gateway restart
# 5. Open an agent session and invoke the skill
# The skill will prompt for your Honcho API key and run setup interactivelyIf you have existing workspace memory files (USER.md, MEMORY.md, IDENTITY.md, memory/, canvas/, etc.), openclaw honcho setup will detect them and offer to migrate them.
Migration is non-destructive — files are uploaded to Honcho. Originals are never deleted or moved.
User/owner files (content describes the user):
USER.md,MEMORY.md- All files in
memory/andcanvas/directories (treated as user content)
Agent/self files (content describes the agent):
SOUL.md,IDENTITY.md,AGENTS.md,TOOLS.md,BOOTSTRAP.md
Files are uploaded via session.uploadFile(). User/owner files go to the owner peer; agent/self files go to the agent peer (agent-{agentId}, e.g. agent-main).
The plugin ships template files in node_modules/@honcho-ai/openclaw-honcho/workspace_md/. Copy or merge these templates into your workspace for AGENTS.md, SOUL.md, and BOOTSTRAP.md. These templates reference the Honcho tools (honcho_profile, honcho_context, honcho_search, honcho_recall, honcho_analyze) instead of the old file-based memory system.
Run openclaw honcho setup to configure interactively, or set values directly in ~/.openclaw/openclaw.json under plugins.entries["openclaw-honcho"].config.
| Key | Type | Default | Description |
|---|---|---|---|
apiKey |
string |
— | Honcho API key (required for managed; omit for self-hosted). |
workspaceId |
string |
"openclaw" |
Honcho workspace ID for memory isolation. |
baseUrl |
string |
"https://api.honcho.dev" |
API endpoint (for self-hosted instances). |
Run openclaw honcho setup, enter a blank API key, and set the Base URL to your instance (e.g., http://localhost:8000).
For setting up a local Honcho server, see the Honcho local development guide.
Once installed, the plugin works 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, andhoncho_analyzeto retrieve relevant context about the user. - Dual Peer Model — Honcho maintains separate representations: one for the user (preferences, facts, communication style) and one for the agent (personality, learned behaviors).
Honcho handles all reasoning and synthesis in the cloud.
The plugin manages markdown files in your workspace:
| File | Contents |
|---|---|
SOUL.md |
Agent profile — OpenClaw's self-model and personality. |
IDENTITY.md |
Static agent identity. Uploaded to the agent peer in Honcho during setup; the local file is not modified. |
AGENTS.md |
Agent capabilities and tool descriptions. |
TOOLS.md |
Tool definitions and usage instructions for the agent. |
BOOTSTRAP.md |
Initial context and instructions for the agent. |
Migration: Legacy files (USER.md, MEMORY.md, memory/ directory) are uploaded to Honcho during openclaw honcho setup. Originals are preserved in place.
The plugin provides both data retrieval tools (cheap, fast, raw data) and Q&A tools (LLM-powered, direct answers).
| Tool | Description |
|---|---|
honcho_session |
Retrieve conversation history and summaries from the current session. Supports semantic search. |
honcho_profile |
Get the user's peer card — a curated list of their most important facts. |
honcho_search |
Semantic vector search over stored observations. Returns raw memories ranked by relevance. |
honcho_context |
Retrieve Honcho's full representation — a broad view of observations about the user. |
| Tool | Description |
|---|---|
honcho_recall |
Ask a simple factual question (e.g., "What's their name?"). Minimal LLM reasoning. |
honcho_analyze |
Ask a complex question requiring synthesis (e.g., "Describe their communication style"). Medium reasoning. |
openclaw honcho setup # Configure API key and migrate legacy files
openclaw honcho status # Show current installation and setup state
openclaw honcho ask <question> # Query Honcho about the user
openclaw honcho search <query> [-k N] [-d D] # Semantic search over memory (topK, maxDistance)This plugin automatically exposes OpenClaw's memory_search and memory_get tools when a memory backend is configured. This allows you to use both Honcho's cloud-based memory AND local file search together.
-
Install QMD on your server (QMD documentation)
-
Configure OpenClaw to use QMD as the memory backend in
~/.openclaw/openclaw.json:
{
"memory": {
"backend": "qmd",
"qmd": {
"limits": {
"timeoutMs": 120000
}
}
}
}- Set up QMD collections for your files:
qmd collection add ~/Documents/notes --name notes
qmd update- Restart OpenClaw:
openclaw gateway restartWhen QMD is configured, you get both Honcho and local file tools:
| Tool | Source | Description |
|---|---|---|
honcho_* |
Honcho | Cross-session memory, user modeling, dialectic reasoning |
memory_search |
QMD | Search local markdown files |
memory_get |
QMD | Retrieve file content |
OpenClaw runs as a systemd service with a different PATH. Create a symlink:
sudo ln -s ~/.bun/bin/qmd /usr/local/bin/qmdQMD operations can take a while, especially first-time queries that download ~2GB of models. Increase the timeout in ~/.openclaw/openclaw.json:
{
"memory": {
"qmd": {
"limits": {
"timeoutMs": 120000
}
}
}
}The default timeout is 4000ms which depending on your hardware may be too short and cause errors. Setting it to 120000ms (2 minutes) gives QMD enough time. You can verify it's working in the logs:
19:09:02 tool start: memory_search
19:09:14 tool end: memory_search # 12 seconds — within the 120s limit
You can also pre-warm QMD to avoid first-run delays:
qmd query "test"See CONTRIBUTING.md for development setup, building from source, and contribution guidelines.
- GitHub Issues: Open an Issue
- Discord: Join the Community
- X (Twitter): Follow @honchodotdev
- Blog: Read about Honcho and Agents
