#memory wiki
10 messages · Page 1 of 1 (latest)
Let me pull the exact docs for the plugin and CLI so I don’t make up config keys.
I want to verify whether the wiki CLI supports scoping to a specific agent before I tell you the exact commands.
Yep. A couple important bits first:
- The wiki config goes in
~/.openclaw/openclaw.json, not in~/.openclaw/agents/aurora/agent - That
agentDiris mostly auth/model state - Your paths look like the actual agent id is probably
aurora, andjim-ceois the persona/name
If you want a structured wiki for that agent’s knowledge, I’d set memory-wiki up with its vault inside that workspace, like this:
{
plugins: {
entries: {
"memory-wiki": {
enabled: true,
config: {
vaultMode: "bridge", // use "isolated" if you want a manual wiki first
vault: {
path: "~/.openclaw/workspace/aurora/wiki",
renderMode: "native" // or "obsidian"
},
bridge: {
enabled: true,
readMemoryArtifacts: true,
indexDreamReports: true,
indexDailyNotes: true,
indexMemoryRoot: true,
followMemoryEvents: true
},
search: {
backend: "shared",
corpus: "all"
},
context: {
includeCompiledDigestPrompt: false
},
render: {
preserveHumanBlocks: true,
createBacklinks: true,
createDashboards: true
}
}
}
}
}
}
Then restart and initialize it:
openclaw gateway restart
openclaw wiki status
openclaw wiki doctor
openclaw wiki init
openclaw wiki bridge import
openclaw wiki compile
openclaw wiki lint
My recommendation:
- use
bridgeifauroraalready has useful memory and you want the wiki built from that - use
isolatedif you want a clean curated wiki that you grow intentionally