Honcho for OpenClaw plugin
Honcho memory plugin for OpenClaw: separate models of the user and the agent and honcho tools beside the built-in memory.
- 95 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Conversations and uploaded memory files are sent to the external Honcho service.
Install
- Works in
Manual install
openclaw plugins install @honcho-ai/openclaw-honchoThen `openclaw plugins enable openclaw-honcho`, the `allowConversationAccess` flag and `openclaw honcho setup`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Conversations and uploaded memory files are sent to the external Honcho service.
This is third-party code. Review the repository files before installing.
What it does
The plugin connects Honcho to OpenClaw as memory with dialectic reasoning: the service builds and maintains separate models of the user and the agent so conversations use accumulated context. The plugin does not replace the built-in `memory-core` memory. It keeps the slot and the file-based store, while Honcho adds its own `honcho_*` tools, prompt guidance and message capture. The tools include `honcho_context`, `honcho_search_conclusions`, `honcho_ask`, `honcho_search_messages` and `honcho_session`. The `openclaw honcho setup` command asks for a Honcho API key, writes the config and optionally uploads legacy memory files. No local infrastructure is required.
Who it is for. OpenClaw users who want the agent to remember people and context across sessions without running a memory server of their own.
Good fit when
- The agent should account for owner preferences accumulated over weeks of dialogue.
- Old USER.md, MEMORY.md and note files must move into long-term memory.
- You need to search conclusions and messages from past sessions.
- The built-in memory stays and a separate layer of understanding people is added to it.
Not a fit when
- Conversation content cannot be sent to an external service.
- You need fully local memory with no API key.
- You do not use OpenClaw.
Example request
Use honcho to recall what I said about project plans last week and compare it with the current task.Limitations
Saving new messages to Honcho requires the `allowConversationAccess` flag, and without it the plugin logs a warning at startup. You need a Honcho API key, and conversations and uploaded memory files go to that service. Migration is non-destructive: originals are not deleted or moved, user files go to the owner peer and agent files to the `agent-{agentId}` peer. Versions before 1.7.0 took the memory slot, and after upgrading the plugin clears the old value itself, printing the recovery command `openclaw config unset plugins.slots.memory` if settings are locked.
How to disable. Disable the plugin with `openclaw plugins disable openclaw-honcho` and restart the gateway with `openclaw gateway restart`. Delete data in Honcho through the service itself.
FAQ
Does the plugin replace built-in memory?
No, `memory-core` keeps the memory slot and file store. Honcho adds its own tools, prompt guidance and message capture beside it.
What does the allowConversationAccess flag do?
It lets the plugin save new messages to Honcho. Without it a startup warning appears and saving does not work.
How do I migrate old memory files?
`openclaw honcho setup` finds files such as USER.md, MEMORY.md, SOUL.md and the memory and canvas folders and offers to upload them. Originals stay in place.
Do I need my own server?
No, no local infrastructure is required. You need a Honcho API key.
Where are the plugin settings?
In `~/.openclaw/openclaw.json` under `plugins.entries["openclaw-honcho"].config`, or through the interactive `openclaw honcho setup` command.
Discussion
No questions or reviews yet.
Related
PluginsHoncho plugins from Plastic Labs: Claude Code memory that survives sessions and skills for wiring the Honcho SDK into your app.
Long-term memory for OpenCode: preferences and project decisions survive restarts, context wipes and fresh chats.
Honcho MCP gives an agent memory about a user: it stores conclusions from conversations and answers questions about them.
Hook and skill for OpenClaw: reorganize the memory and knowledge folders into L0/L1/L2 layers with a relation graph
ClawMem gives Claude Code, OpenClaw and Hermes local memory: note search, session hooks and a 33-tool MCP server with no API keys
A long-term memory plugin for the OpenClaw agent on LanceDB: captures preferences and decisions itself, hybrid search, noise fading
README in short
The plugin works beside `memory-core` and adds Honcho dialectic memory. It ships templates for AGENTS.md, SOUL.md and BOOTSTRAP.md that refer to Honcho tools and a honcho-setup skill for ClawHub.