fix: add contracts.tools to plugin manifest for OpenClaw >= 2026.5.2 - #4
Open
fmfsaisai wants to merge 1 commit into
Open
fix: add contracts.tools to plugin manifest for OpenClaw >= 2026.5.2#4fmfsaisai wants to merge 1 commit into
fmfsaisai wants to merge 1 commit into
Conversation
OpenClaw v2026.5.2 introduced mandatory tool contract enforcement in the plugin registry. Plugins that call api.registerTool() must now declare their tool names in openclaw.plugin.json under contracts.tools, otherwise registerTool() silently skips registration and pushes an error diagnostic. Without this change, conversation_archive_search and conversation_archive_health tools are not available to agents on OpenClaw >= 2026.5.2, even though the plugin loads successfully and hooks work fine. Verified on OpenClaw 2026.5.2: - Before: plugins inspect shows "ERROR: plugin must declare contracts.tools before registering agent tools", Tools section empty - After: Tools section shows both tools, no diagnostics errors
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OpenClaw v2026.5.2 introduced mandatory tool contract enforcement in the plugin registry (changelog entry). Plugins that call
api.registerTool()must now declare their tool names inopenclaw.plugin.jsonundercontracts.tools. Without this declaration,registerTool()silently skips registration and pushes an error diagnostic — the plugin loads fine and hooks work, but tools are not available to agents.This PR adds the missing
contracts.toolsdeclaration forconversation_archive_searchandconversation_archive_health.Changes
openclaw.plugin.json: addedcontracts.toolsarray listing both registered tool namesVerification
Tested on OpenClaw 2026.5.2 (
openclaw plugins inspect conversation-archive --runtime):Before (without
contracts.tools):Tools section absent — tools not registered.
After (with
contracts.tools):No diagnostics errors. Both tools registered successfully.
Context
The
contracts.toolsenforcement was added in OpenClaw v2026.5.2 as part of the manifest-first control plane direction. This is a breaking change for plugins that register tools without declaring them in the manifest. The plugin's 0.2.0 release predates this change (April 9 vs May 2), which is why it wasn't caught earlier.