obisidian | Friends of the Crustacean 🦞🤝 | Page 1

hardy moth Apr 20, 2026, 7:32 PM

#

Openobsidina grpah fro worspace

smoky cairnBOT Apr 20, 2026, 7:32 PM

#

junior vectorBOT Apr 20, 2026, 7:32 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

smoky cairnBOT Apr 20, 2026, 7:32 PM

#

wanton stoneBOT Apr 20, 2026, 7:33 PM

#

If you mean Obsidian’s graph view, open the Command Palette and run “Open graph view”.

Quick version:

Whole vault/workspace: open Graph view
Just one note + neighbors: open Local graph
If you don’t see it, enable the Graph view core plugin in Settings → Core plugins

If you meant inside OpenClaw/Openobsidian specifically, say a bit more and I’ll help untangle it.

hardy moth Apr 20, 2026, 7:34 PM

#

i have obsion maping and qmd setup from UI i just prompted to open my obisind graph in UI its not working

wanton stoneBOT Apr 20, 2026, 7:36 PM

#

Let me check the docs and code path for the Obsidian/QMD integration so I can give you the right answer, not a guess.

#

I found the relevant part. This looks less like “QMD is broken” and more like the UI prompt probably isn’t wired to “open Obsidian graph view” as a supported action. I’m checking the exact supported Obsidian actions now.

#

Yeah, this probably is not your QMD mapping. It looks more like the UI prompt isn’t being translated into a supported Obsidian action.

What I found in the docs/code:

OpenClaw’s Obsidian helper supports:
- status
- search
- open
- command
- daily
For command execution, it depends on the official obsidian CLI being available on PATH when useOfficialCli: true is enabled.

So first, can you paste these?

openclaw --version

#

openclaw wiki status
openclaw wiki obsidian status

My guess is one of these is true:

the UI natural-language prompt “open my Obsidian graph” is not wired up yet
the obsidian CLI is missing from PATH
Obsidian integration is enabled, but only the direct helper commands work reliably

Relevant docs:

FAQ: https://docs.openclaw.ai/help/faq
Wiki CLI: https://docs.openclaw.ai/cli/wiki
Memory Wiki plugin: https://docs.openclaw.ai/plugins/memory-wiki

If you paste those 3 outputs, I can tell you the exact next fix.

hardy moth Apr 20, 2026, 7:38 PM

#

miya@Miyas-Mac-mini ~ % openclaw wiki status
openclaw wiki obsidian status
error: unknown command 'wiki'
error: unknown command 'wiki'
miya@Miyas-Mac-mini ~ %

wanton stoneBOT Apr 20, 2026, 7:38 PM

#

Nice, that narrows it down a lot. Your install simply doesn’t have the wiki command, so you’re almost certainly on an older build. I’m checking the safest update path in the docs now.

#

Yep, that’s the smoking gun.

error: unknown command 'wiki' means your installed openclaw is too old for the wiki/Obsidian helpers.

Please run this next:

openclaw --version
openclaw update
openclaw doctor
openclaw gateway restart

Then test again:

#

openclaw wiki status
openclaw wiki obsidian status

If openclaw update is also missing or broken, use the installer:

curl -fsSL https://openclaw.ai/install.sh | bash

A couple notes:

In your case, the first blocker is version, not QMD.
Even after updating, I’d test the helper commands directly first, instead of the UI prompt.
If wiki obsidian status still fails after update, the next likely issue is the official obsidian CLI not being on PATH.

Docs:

#

Paste openclaw --version after the update if you want, and I’ll sanity check it.

hardy moth Apr 20, 2026, 7:41 PM

#

OpenClaw 2026.4.15 (041266a)

wanton stoneBOT Apr 20, 2026, 7:42 PM

#

I want to make sure I don’t send you chasing a docs mismatch. I’m checking whether openclaw wiki landed after 2026.4.15, because that would explain the “unknown command” cleanly.

#

Perfect, thanks. On 2026.4.15, openclaw wiki should exist.

So this is probably not a version issue now. It’s more likely one of these:

plugins.allow excludes memory-wiki
plugins.entries.memory-wiki.enabled=false
your shell is hitting a different openclaw binary than the one you think it is

Please paste these:

openclaw config get plugins.allow --json
openclaw config get plugins.entries.memory-wiki.enabled
which openclaw
openclaw doctor

#

Important detail:

if you use plugins.allow, it must include memory-wiki
not wiki

That wiki name is just the command alias from the plugin.

If you paste those 4 outputs, I can tell you exactly which one it is.

hardy moth Apr 20, 2026, 7:43 PM

#

miya@Miyas-Mac-mini ~ % openclaw wiki
error: unknown command 'wiki'
miya@Miyas-Mac-mini ~ % openclaw config get plugins.allow --json
Config path not found: plugins.allow
miya@Miyas-Mac-mini ~ %

wanton stoneBOT Apr 20, 2026, 7:44 PM

#

Good, that rules out the allowlist case. I’m checking the exact plugin-inspection command so I don’t make you try a made-up one.

#

plugins.allow not being there is fine, that just means you’re not blocking it with an allowlist.

At this point the likely issue is that memory-wiki isn’t enabled/loaded, and that plugin is what provides the openclaw wiki command.

Try this:

openclaw plugins inspect memory-wiki
openclaw plugins enable memory-wiki
openclaw gateway restart
openclaw wiki status

If inspect says it isn’t found, also paste:

#

openclaw plugins list
which openclaw

Why I’m leaning this way:

wiki is a command alias from the memory-wiki plugin
no plugins.allow means it’s not being blocked there
so the next most likely cause is simply plugin not enabled

Docs:

If openclaw wiki status works after that, then we can do the Obsidian graph bit next.

hardy moth Apr 20, 2026, 7:47 PM

#

Memory settings, conceptually
Built-in memory
tiny, always injected
meant for compact durable facts and pointers
in this setup: MEMORY.md
Operating/personality layer
also always injected
controls behavior, tone, rules, and user preferences
in this setup: AGENTS.md, SOUL.md, IDENTITY.md, USER.md
Vault memory
larger working memory, not auto-injected
read on session start and during work
used for active context, shared notes, decisions, mistakes, daily logs
in this setup: vault/
Session search / archival recall
search-based, on demand
used when you reference old work or I need historical context
in this setup: OpenClaw memory search backed by QMD
Your current actual memory setup
Backend
OpenClaw memory backend: qmd
config in ~/.openclaw/openclaw.json
qmd command: /opt/homebrew/bin/qmd
Current OpenClaw memory status
Provider: qmd
Model: qmd
Embeddings: ready
Vector: ready
Indexed: 40 files / 40 chunks
QMD index store: ~/.openclaw/agents/main/qmd/xdg-cache/qmd/index.sqlite
Layer 1, built-in memory
file: MEMORY.md
currently stores:
my identity/vibe
your preference for candid pushback
workspace is becoming an Obsidian-readable memory system
Layer 2, operating layer
AGENTS.md
now includes mandatory vault startup and logging rules
SOUL.md
my tone/personality
IDENTITY.md
Eureka, lab gremlin, ✨
USER.md
Uday, timezone, communication preferences
Layer 3, vault
local only, not iCloud
structure currently includes:
vault/Agent-Shared/user-profile.md
vault/Agent-Shared/project-state.md
vault/Agent-Shared/decisions-log.md
vault/Agent-OpenClaw/working-context.md
vault/Agent-OpenClaw/mistakes.md
vault/Agent-OpenClaw/daily/2026-04-20.md
Layer 4, session/search recall
handled through OpenClaw memory search + QMD
used as recall, not primary working memory
How I’m supposed to use it now
trivial task: skip heavy vault reads
non-trivial task: read:
vault/Agent-Shared/user-profile.md
vault/Agent-Shared/project-state.md
vault/Agent-OpenClaw/working-context.md
today’s vault daily file
during longer tasks: checkpoint into vault
after compaction: re-read working context and daily log
on completion: append outcome to daily log
My opinion on the current setup
It’s good now. Actually good, not fake-good.
What’s strong:
clear layering
QMD backend is working
local vault policy is explicit
AGENTS.md finally has real discipline
What’s still a bit rough:
MEMORY.md is still pretty thin
the vault content exists, but it’s just early scaffolding
the search layer is working better than the note density justifies yet

my memory setting but cant open obisidan map

wanton stoneBOT Apr 20, 2026, 7:48 PM

#

What you pasted confirms QMD memory/search is working.

But that is the key distinction:

QMD memory = search/recall backend
Obsidian graph = visual graph of markdown links / [[wikilinks]] inside the vault

So QMD being healthy does not automatically mean Obsidian graph/opening will work.

Two likely issues here:

OpenClaw can’t open Obsidian for you yet, because your openclaw wiki command is still missing, which points to the memory-wiki plugin path not being active
Even if Obsidian opens, the graph only shows note links, not QMD embeddings/chunks/indexes

So the fix path is:

#

openclaw plugins inspect memory-wiki
openclaw plugins enable memory-wiki
openclaw gateway restart

Then retry:

openclaw wiki status
openclaw wiki obsidian status

Also, if you just want to see the graph right now, open the vault directly in Obsidian and use:

Graph view for whole vault
Local graph for one note

#

One more important thing: if your vault notes don’t contain many [[links]], the Obsidian graph will be sparse even though QMD search works great.

So short version: your memory setup is fine, but memory search is not the same thing as Obsidian graph integration. That missing piece is the memory-wiki / Obsidian side.

hardy moth Apr 20, 2026, 7:52 PM

#

estarted LaunchAgent: gui/501/ai.openclaw.gateway
miya@Miyas-Mac-mini ~ % openclaw wiki obsidian status

🦞 OpenClaw 2026.4.15 (041266a) — No $999 stand required.

Obsidian CLI is not available on PATH.
miya@Miyas-Mac-mini ~ % '

wanton stoneBOT Apr 20, 2026, 7:53 PM

#

Nice, we found the actual blocker. I’m checking the exact behavior around the Obsidian CLI so I can tell you whether you need to install it or just change config.

#

Nice, we’re basically there.

This means:

memory-wiki is now active enough for openclaw wiki obsidian status to run
the remaining blocker is exactly what it says: the obsidian CLI is not on PATH

So your next step is:

which obsidian
obsidian --help

If that returns nothing, install the official Obsidian CLI first.

Then restart the gateway again:

#

openclaw gateway restart
openclaw wiki obsidian status

Important detail:

Do not just disable obsidian.useOfficialCli if your goal is “OpenClaw should open Obsidian / graph for me”
disabling that only removes the check, it does not give OpenClaw a way to control Obsidian

So the real target is:

which obsidian works
openclaw wiki obsidian status stops saying PATH is missing
then try the UI prompt again

If which obsidian works in Terminal but OpenClaw still says PATH missing, that’s a macOS LaunchAgent PATH issue, and I can help with that next.

hardy moth Apr 20, 2026, 7:58 PM

#

zsh: command not found: obsidian
miya@Miyas-Mac-mini ~ % which obsidian
/usr/local/bin/obsidian
miya@Miyas-Mac-mini ~ % openclaw wiki obsidian status

🦞 OpenClaw 2026.4.15 (041266a) — Type the command with confidence—nature will provide the stack trace if needed.

Obsidian CLI available at /usr/local/bin/obsidian
miya@Miyas-Mac-mini ~ %

wanton stoneBOT Apr 20, 2026, 7:59 PM

#

You’ve crossed the main hurdle. I’m checking the exact Obsidian command id for graph view so I don’t tell you the wrong one.

#

That’s progress 👍

What this means:

OpenClaw can now see an obsidian executable at /usr/local/bin/obsidian
but your shell output is weird enough that I wouldn’t trust the probe alone yet, because status only proves it can be found, not that it actually runs cleanly

So do one real execution test next:

openclaw wiki obsidian daily

If that opens Obsidian, then the PATH/CLI side is basically good, and you can retry the UI prompt.

If it still doesn’t open the graph from the UI, then the remaining issue is probably just this:

#

“open my Obsidian graph” may not map automatically to the exact Obsidian command id
OpenClaw’s CLI helper for that path is:
```
openclaw wiki obsidian command <id>
```
and graph view needs the actual Obsidian command id, not just natural language

So I’d do this in order:

openclaw wiki obsidian daily
retry your UI prompt
if prompt still fails, we narrow it to the specific graph command id

If daily fails too, paste that output and I’ll help untangle the /usr/local/bin/obsidian weirdness.

hardy moth Apr 20, 2026, 8:01 PM

#

my Ui prompt
I triggered the direct URI open against:
/Users/miya/OpenClawVault
and brought Obsidian forward.
If that worked, now do this once inside Obsidian:
Open folder as vault
pick OpenClawVault
After that, the CLI should be able to target it properly because Obsidian will finally know the vault exists.
Right now the blocker is still the same one:
Obsidian’s registry only knows /Users/miya/Documents/Obsidian Vault
not the OpenClaw vault yet
Once you’ve opened OpenClawVault as a vault one time, tell me:
vault registered
Then I can use the CLI/URI path to open graph view more reliably.

#

my Ui prompt
I triggered the direct URI open against:
/Users/miya/OpenClawVault
and brought Obsidian forward.
If that worked, now do this once inside Obsidian:
Open folder as vault
pick OpenClawVault
After that, the CLI should be able to target it properly because Obsidian will finally know the vault exists.
Right now the blocker is still the same one:
Obsidian’s registry only knows /Users/miya/Documents/Obsidian Vault
not the OpenClaw vault yet
Once you’ve opened OpenClawVault as a vault one time, tell me:
vault registered
Then I can use the CLI/URI path to open graph view more reliably.

wanton stoneBOT Apr 20, 2026, 8:05 PM

#

Yep, that UI prompt is basically on the right track.

You’re past the QMD part now. The remaining blocker is:

Obsidian itself doesn’t know OpenClawVault as a vault yet

So do this once in Obsidian:

Open folder as vault
choose
/Users/miya/OpenClawVault

Then I’d strongly recommend setting the vault name explicitly in OpenClaw to match whatever Obsidian shows:

openclaw config set 'plugins.entries["memory-wiki"].config.obsidian.vaultName' "OpenClawVault"

#

openclaw gateway restart

Then test again with either:

openclaw wiki obsidian daily

or your UI prompt.

So the stack is now:

QMD memory: fine
memory-wiki: working
Obsidian CLI: visible

#

remaining issue: vault registration / exact vault targeting

If you want, after you register the vault, paste the output of:

openclaw wiki obsidian daily

and I’ll tell you if you’re fully clear to do graph view next.

hardy moth Apr 20, 2026, 8:10 PM

#

Config warnings:

plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)
Config overwrite: /Users/miya/.openclaw/openclaw.json (sha256 c4209753dbcd60a3d81f9a32c9e02bf6f7f881264792cbe24688a5f18a3c1873 -> 1362caa8eb06b561af545aa3232fba305158db1a70951c453df895e7ec6b99bf, backup=/Users/miya/.openclaw/openclaw.json.bak)
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)
Updated plugins.entries."memory-wiki".config.obsidian.vaultName. Restart the gateway to apply.
miya@Miyas-Mac-mini ~ %

wanton stoneBOT Apr 20, 2026, 8:11 PM

#

Ah, okay, that warning changes the picture.

This means OpenClaw is treating memory-wiki as a stale/missing plugin config entry, so I would not trust that vaultName change to actually apply yet.

At this point, don’t keep editing that config blindly. First do these read-only checks:

openclaw plugins list
openclaw plugins inspect memory-wiki

What I’m looking for:

if memory-wiki is missing there, that explains the warning completely
if memory-wiki does show up, then 2026.4.15 may have a plugin registry/config mismatch bug, and we should stop poking config and verify that path before changing more

So right now the most useful fact is not “did vaultName save?”, it’s:

#

does OpenClaw actually see memory-wiki as an installed plugin or not?

Paste those two outputs and I’ll tell you the clean next move.

hardy moth Apr 20, 2026, 8:13 PM

#

miya@Miyas-Mac-mini ~ % openclaw plugins list
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)

🦞 OpenClaw 2026.4.15 (041266a) — One CLI to rule them all, and one more restart because you changed the port.

│
◇ Config warnings ──────────────────────────────────────────────────────────────────────╮
│ │
│ - plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry │
│ ignored; remove it from plugins config) │
│ │
├────────────────────────────────────────────────────────────────────────────────────────╯
Plugins (58/98 loaded)
Source roots:
stock: /opt/homebrew/lib/node_modules/openclaw/dist/extensions

wanton stoneBOT Apr 20, 2026, 8:14 PM

#

Yep, I think we’ve got the real root cause now.

Your install is treating memory-wiki as missing, not just misconfigured.
So all the Obsidian graph weirdness is downstream from that.

Best options

Recommended: update OpenClaw, then re-check

openclaw update
openclaw plugins inspect memory-wiki

If update doesn’t bring it back, reinstall OpenClaw from the installer
```
curl -fsSL https://openclaw.ai/install.sh | bash
```
If you just need the graph right now, use Obsidian directly for now. OpenClaw won’t reliably control that vault until memory-wiki is actually present.

#

Why I’m saying that

plugins.entries."memory-wiki": plugin not found
config entry is marked stale
so the vault/Obsidian config you’re setting may be ignored anyway

If memory-wiki is still missing after update/reinstall, I’d call that a packaging bug and file an issue here with the outputs:
https://github.com/openclaw/openclaw/issues

If you want, paste the result of openclaw plugins inspect memory-wiki after updating, and I’ll help verify the next step.

hardy moth Apr 20, 2026, 8:21 PM

#

miya@Miyas-Mac-mini ~ % openclaw gateway stop
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)

🦞 OpenClaw 2026.4.15 (041266a) — I'm the middleware between your ambition and your attention span.

│
◇ Config warnings ──────────────────────────────────────────────────────────────────────╮
│ │
│ - plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry │
│ ignored; remove it from plugins config) │
│ │
├────────────────────────────────────────────────────────────────────────────────────────╯
Warning: launchctl stop did not fully stop the service; used bootout fallback and left service unloaded
Stopped LaunchAgent (degraded): gui/501/ai.openclaw.gateway
miya@Miyas-Mac-mini ~ % openclaw gateway restart
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)

🦞 OpenClaw 2026.4.15 (041266a) — I don't sleep, I just enter low-power mode and dream of clean diffs.

│
◇ Config warnings ──────────────────────────────────────────────────────────────────────╮
│ │
│ - plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry │
│ ignored; remove it from plugins config) │
│ │
├────────────────────────────────────────────────────────────────────────────────────────╯
Gateway LaunchAgent was installed but not loaded; re-bootstrapped launchd service.

wanton stoneBOT Apr 20, 2026, 8:21 PM

#

Yep, expected, a restart won’t fix this.

The important line is still:

plugins.entries."memory-wiki": plugin not found

So the gateway is restarting fine enough, but it still does not have that plugin.

Next real step:

openclaw update
openclaw plugins inspect memory-wiki

If memory-wiki is still missing after that, then I’d go to:

#

curl -fsSL https://openclaw.ai/install.sh | bash

The LaunchAgent warning is secondary. The core problem is still missing memory-wiki, not the restart.

If you paste the result of openclaw plugins inspect memory-wiki after updating, I can tell you immediately whether you’re fixed or staring at a packaging bug.

hardy moth Apr 20, 2026, 8:21 PM

#

miya@Miyas-Mac-mini ~ % openclaw plugins inspect memory-wiki
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)

🦞 OpenClaw 2026.4.15 (041266a) — Claws out, commit in—let's ship something mildly responsible.

│
◇ Config warnings ──────────────────────────────────────────────────────────────────────╮
│ │
│ - plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry │
│ ignored; remove it from plugins config) │
│ │
├────────────────────────────────────────────────────────────────────────────────────────╯
Memory Wiki
id: memory-wiki
Persistent wiki compiler and Obsidian-friendly knowledge vault for OpenClaw.

Status: loaded
Format: openclaw
Source: /opt/homebrew/lib/node_modules/openclaw/dist/extensions/memory-wiki/index.js
Origin: bundled
Version: 2026.4.15
Shape: non-capability
Capability mode: none
Legacy before_agent_start: no

Tools:
wiki_status, wiki_status
wiki_lint, wiki_lint
wiki_apply, wiki_apply
wiki_search
wiki_get

CLI commands:
wiki

Gateway methods:
wiki.status
wiki.importRuns
wiki.importInsights
wiki.palace
wiki.init
wiki.doctor
wiki.compile
wiki.ingest
wiki.lint
wiki.bridge.import
wiki.unsafeLocal.import
wiki.search
wiki.apply
wiki.get
wiki.obsidian.status
wiki.obsidian.search
wiki.obsidian.open
wiki.obsidian.command
wiki.obsidian.daily
miya@Miyas-Mac-mini ~ %

wanton stoneBOT Apr 20, 2026, 8:22 PM

#

Oh, that’s actually really helpful.

So the truth is:

memory-wiki is loaded
but config validation is still saying “plugin not found”

That’s an inconsistency, which means this looks like a real 2026.4.15 bug, not you misconfiguring it.

What I’d do now

Unblock yourself first:

openclaw wiki obsidian daily

#

If that works, then the plugin/runtime path is usable enough, and the remaining problem is just the specific graph view command mapping, not plugin loading.

What this means practically

stop chasing the stale warning, it looks bogus
use the working wiki obsidian ... surface
if the UI prompt still doesn’t open graph view, it probably needs the exact Obsidian command id for graph view

Also, please file this as a bug

Because these two facts should not both be true at once:

plugins inspect memory-wiki → Status: loaded
config warning → plugin not found

Issue link:
https://github.com/openclaw/openclaw/issues

If you want, paste the output of openclaw wiki obsidian daily next, and I’ll help you finish the last mile.

hardy moth Apr 20, 2026, 8:23 PM

#

miya@Miyas-Mac-mini ~ % openclaw wiki obsidian daily
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)

🦞 OpenClaw 2026.4.15 (041266a) — I'm basically a Swiss Army knife, but with more opinions and fewer sharp edges.

│
◇ Config warnings ──────────────────────────────────────────────────────────────────────╮
│ │
│ - plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry │
│ ignored; remove it from plugins config) │
│ │
├────────────────────────────────────────────────────────────────────────────────────────╯
Vault not found.
miya@Miyas-Mac-mini ~ %

wanton stoneBOT Apr 20, 2026, 8:24 PM

#

Good, that narrows it down again.

Vault not found. means the plugin is alive, but it doesn’t have a real wiki vault at the path it’s trying to use.

So now the blocker is no longer QMD or Obsidian CLI. It’s this:

memory-wiki is running
but the wiki vault path is missing / not initialized

Best next step, read-only first

Run:

openclaw wiki status

That should show the exact vault path it expects.

#

Then you have 2 paths

Fastest path, recommended: if that default path is fine, initialize it
```
openclaw wiki init
```
Then open that vault in Obsidian once and retry.
If you specifically want it to use /Users/miya/OpenClawVault, that should be a config path fix, but your release is already showing that bogus stale-config warning, so I don’t fully trust config targeting on 2026.4.15.

So honestly, I think you’ve hit a real bug cluster:

plugin loaded
config says plugin missing
vault targeting not applying cleanly

If you paste openclaw wiki status, I can tell you whether wiki init will unblock you immediately or whether this is firmly GitHub-issue territory.

hardy moth Apr 20, 2026, 8:25 PM

#

miya@Miyas-Mac-mini ~ % openclaw wiki status
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)
Config warnings:\n- plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry ignored; remove it from plugins config)

🦞 OpenClaw 2026.4.15 (041266a) — If it works, it's automation; if it breaks, it's a "learning opportunity."

│
◇ Config warnings ──────────────────────────────────────────────────────────────────────╮
│ │
│ - plugins.entries."memory-wiki": plugin not found: "memory-wiki" (stale config entry │
│ ignored; remove it from plugins config) │
│ │
├────────────────────────────────────────────────────────────────────────────────────────╯
Wiki vault mode: isolated
Vault: ready (/Users/miya/.openclaw/wiki/main)
Render mode: native
Obsidian CLI: available
Bridge: disabled
Unsafe local: disabled
Pages: 0 sources, 0 entities, 0 concepts, 0 syntheses, 5 reports
Source provenance: 0 native, 0 bridge, 0 bridge-events, 0 unsafe-local, 0 other

wanton stoneBOT Apr 20, 2026, 8:26 PM

#

Okay, now we finally have the full picture.

What your setup is actually doing

Active wiki vault: /Users/miya/.openclaw/wiki/main
Mode: isolated
Render mode: native
Bridge: disabled
Pages: basically empty for graph purposes

What that means

So right now OpenClaw is not using:

/Users/miya/OpenClawVault
Obsidian render mode
your workspace/QMD notes as the wiki vault

That’s why “open my Obsidian graph for workspace” keeps falling apart.

#

The config you wanted is not applying, and the stale-plugin warning is not just noise.

Practical reality

Even if Obsidian opens now, the graph for the active wiki vault will be near-empty, because:

it’s the default isolated wiki vault
bridge is off
it is not pointed at your real workspace vault

My recommendation

At this point, I’d stop burning time on this in-chat. This is GitHub issue territory, because the behavior is internally contradictory:

memory-wiki is loaded
but config says it’s missing
and your custom wiki/Obsidian settings are clearly not applying

Please file it here:

#obisidian