#Honcho and memory-wiki
10 messages ยท Page 1 of 1 (latest)
Yes, they can work together.
Short version:
- Honcho = the active memory system, cross-session recall + user modeling
- memory-wiki = a companion layer that compiles memory into a wiki/vault
So memory-wiki does not replace Honcho, it sits beside it.
Basic setup
- Install + set up Honcho:
openclaw plugins install @honcho-ai/openclaw-honcho
openclaw honcho setup
- Enable
memory-wikiin your config (JSON5), usually with bridge mode if you want it to organize Honcho-backed memory:
{
plugins: {
entries: {
"openclaw-honcho": {
config: {
apiKey: "your-api-key",
workspaceId: "openclaw",
baseUrl: "https://api.honcho.dev",
},
},
"memory-wiki": {
enabled: true,
config: {
vaultMode: "bridge",
vault: {
path: "~/.openclaw/wiki/main",
renderMode: "obsidian",
},
bridge: {
enabled: true,
readMemoryArtifacts: true,
followMemoryEvents: true,
indexDreamReports: true,
indexDailyNotes: true,
indexMemoryRoot: true,
},
search: {
backend: "shared",
corpus: "all",
},
},
},
},
},
}
- Restart the gateway:
openclaw gateway restart
- Verify:
openclaw honcho status
openclaw wiki status
openclaw wiki bridge import
openclaw wiki compile
Recommendation
If you just want better memory, start with Honcho only.
Add memory-wiki if you also want:
- a browsable wiki vault
- structured claims/provenance
- dashboards/syntheses
- Obsidian-friendly output
Docs:
- Honcho: https://docs.openclaw.ai/concepts/memory-honcho
- Memory Wiki: https://docs.openclaw.ai/plugins/memory-wiki
- Memory overview: https://docs.openclaw.ai/concepts/memory
If you want, I can also give you a minimal combined config for local/self-hosted Honcho or hosted Honcho.