MemOS Cloud Plugin 初始化后仍提示 configuration not found

[Memtensor-AI]

安装 MemOS Cloud Plugin 后执行初始化命令，配置文件已生成，但插件启动时仍提示 configuration not found；重启后问题不变。现象表明初始化写入的配置未被插件正确识别，疑似配置读取路径或初始化链路异常。

[Memtensor-AI]

🤖 AutoDev has picked up this issue and started working on it.

Task ID: 0b3ecc3e987c54e9
Working branch: bugfix/autodev-161-20260902065629783
Target branch: main
Workflow: opsp (analysis → coding → testing → PR)

I will post the PR link here once done. If I need more information, I will ask in the comments.

[Memtensor-AI]

🤔 AutoDev task 0b3ecc3e987c54e9 needs clarification to proceed:
Hi, thanks for filing #161. Before I can safely fix this I need to confirm the reproduction path, because the literal string "configuration not found" does not appear anywhere in this plugin's source code (I grepped index.js and every file under lib/, including lib/config-ui/). That means the message is coming from either the OpenClaw host CLI or is a paraphrase of a related plugin log, and each interpretation leads to a different fix. Could you clarify:

1. Is "configuration not found" the exact log/error text, or a summary of what you observed? If it's the exact text, please paste the full log line plus ~3 lines of context above and below it, and tell us which command produced it (e.g. openclaw gateway start, openclaw plugins install ..., openclaw plugins list, config UI page in the browser, etc.) and which host binary (openclaw / moltbot / clawdbot).

2. What exactly is "the initialization command" you ran? For example: openclaw plugins install @memtensor/memos-cloud-openclaw-plugin@latest, a host openclaw config init command, opening the config UI page (default http://127.0.0.1:38463) and saving a filled-in form, or a custom script?

3. Which config file was "generated"? Please paste its contents (with the apiKey redacted). Common candidates are ~/.openclaw/openclaw.json, ~/.openclaw/.env, ~/.moltbot/moltbot.json, ~/.clawdbot/clawdbot.json. Path + full contents (redacted) tells us whether the plugin entry / hooks / config keys are present and well-formed.

4. Reproduction environment: plugin version (from ~/.openclaw/extensions/memos-cloud-openclaw-plugin/package.json version), host CLI version (openclaw / moltbot / clawdbot), OS + Node version.

Once we have (1) + (3) we can pinpoint whether the issue is a runtime-profile misdetection (openclaw vs moltbot vs clawdbot writing to the wrong JSON), a race between the auto hook-policy patcher and the user's UI save (which could drop the config sub-tree), an env-file parsing issue (export KEY=... vs KEY=...), or a schema-mismatch complaint from a newer OpenClaw host that this plugin's manifest hasn't caught up to. Reply with /autodev confirm yes <your answers> to continue.
Suggested default assumption: If the reporter cannot easily produce the requested data, a safe default assumption is: the message comes from the plugin's own "[memos-cloud] Missing MEMOS_API_KEY" warning after the user only edited the config UI without also placing MEMOS_API_KEY in ~/.openclaw/.env, and the confusion is that the UI-side config was saved to openclaw.json but the plugin's runtime cfg object was built before the save (single-process cache). In that case the fix direction is: (a) reload buildConfig after the config UI /api/save writes back so the in-process cfg reflects the new file, and (b) improve the missing-apiKey warning to explicitly mention which file was inspected. This is a plausible starting point but should be confirmed before implementing.
The suggested default is only used if a maintainer explicitly confirms it.
Please reply with one of the following commands (only issue author or repo collaborators):

• /autodev confirm yes — agree and continue with the suggested default assumption
• /autodev confirm no <additional info> — provide more details
• /autodev cancel — cancel this task
  If there is no reply within 24h, AutoDev will cancel this task using the same outcome as /autodev cancel. It will not continue with the suggested default automatically.

[Memtensor-AI]

⏰ AutoDev task 0b3ecc3e987c54e9 received no /autodev confirm reply within 24h. AutoDev cancelled this task using the same outcome as /autodev cancel; it will not continue with the suggested default automatically.