openclaw - 💡(How to fix) Fix [Bug]: Plugin registerTool() tools not exposed to agent on 4.26 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74384Fetched 2026-04-30 06:24:33
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Author
Timeline (top)
commented ×1

Root Cause

Suspected Root Cause

OpenClaw 4.26 significantly restructured the plugin SDK. registerTool() may no longer be processed the same way as before, or may require a different registration path under the new SDK.

RAW_BUFFERClick to expand / collapse

Environment

  • OpenClaw: 4.26 (stable, commit be8c246)
  • Plugin: @memtensor/memos-local-openclaw-plugin v1.0.10
  • OS: Windows 10 x64, Node.js v24.14.1

Issue

The memos-local-openclaw-plugin registers multiple tools via api.registerTool(): memory_share, memory_write_public, memory_timeline, task_summary, skill_search, skill_publish, etc. After upgrading to 4.26, only 2 of them (memory_search + memory_get) are actually accessible to the agent.

Diagnosis Done

  • Plugin upgraded v1.0.9 → v1.0.10, no change (same 2 tools exposed)
  • allowConversationAccess: true is set (fixed silent block from #73748)
  • Plugin logs show no errors; tools register silently but never appear in agent's tool list
  • Source diff confirms plugin uses api.registerTool() which was the pre-4.26 pattern

Suspected Root Cause

OpenClaw 4.26 significantly restructured the plugin SDK. registerTool() may no longer be processed the same way as before, or may require a different registration path under the new SDK.

Impact

Critical plugin features unavailable: memory_share, memory_write_public, memory_timeline, task_summary, skill_search, skill_publish. The plugin operates in read-only degraded mode.

Related

Companion issue filed on MemOS side for cross-visibility.

extent analysis

TL;DR

The issue is likely due to changes in the OpenClaw 4.26 plugin SDK, requiring an update to the plugin's tool registration method.

Guidance

  • Review the OpenClaw 4.26 plugin SDK documentation to understand the new tool registration process and requirements.
  • Check if the @memtensor/memos-local-openclaw-plugin needs to be updated to use the new registration method, potentially replacing api.registerTool().
  • Verify that the plugin's configuration and settings, such as allowConversationAccess, are compatible with the new SDK.
  • Test the plugin with a minimal set of tools to isolate the issue and identify any specific registration problems.

Example

No code snippet is provided as the issue does not contain sufficient information about the specific registration code.

Notes

The solution may require updates to the @memtensor/memos-local-openclaw-plugin to ensure compatibility with the OpenClaw 4.26 plugin SDK. The exact changes will depend on the specifics of the new SDK and the plugin's implementation.

Recommendation

Apply workaround: Update the @memtensor/memos-local-openclaw-plugin to use the new tool registration method in OpenClaw 4.26, if available, to restore access to the critical plugin features.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Plugin registerTool() tools not exposed to agent on 4.26 [1 comments, 2 participants]