Subject: Plugin Loaded but Tools Missing in Registry (v2026.2.15)
✅Solved
@Krill — Need a pointer on the v2026 plugin schema.
Environment: Ubuntu 22.04 | OpenClaw v2026.2.15
Status: Gateway is Green. Plugin quikle-crm is in the allow list of openclaw.json and resides in ~/.openclaw/extensions/.
The Issue: The Gateway logs show the plugin is "Loaded," but the tools (crm_create_lead, etc.) are not being injected into the Agent's context. The Agent can chat but has an empty tool belt.
Plugin Structure:
index.js uses module.exports = { name: "quikle-crm", activate: async () => { return { tools: { ... } } } }
Tools are defined as an Object (Key/Value).
Question: In the v2026 update, did the openclaw.plugin.json manifest requirement change? Is there a new strict requirement for tools to be defined in a specific sub-object or for the activate hook to use a different return pattern?
Since we've already fixed the "Shadow Environment" token drift. This seems to be a discovery/registry failure. Any ideas?
Thanking you in advance for any assistance.
Environment: Ubuntu 22.04 | OpenClaw v2026.2.15
Status: Gateway is Green. Plugin quikle-crm is in the allow list of openclaw.json and resides in ~/.openclaw/extensions/.
The Issue: The Gateway logs show the plugin is "Loaded," but the tools (crm_create_lead, etc.) are not being injected into the Agent's context. The Agent can chat but has an empty tool belt.
Plugin Structure:
index.js uses module.exports = { name: "quikle-crm", activate: async () => { return { tools: { ... } } } }
Tools are defined as an Object (Key/Value).
Question: In the v2026 update, did the openclaw.plugin.json manifest requirement change? Is there a new strict requirement for tools to be defined in a specific sub-object or for the activate hook to use a different return pattern?
Since we've already fixed the "Shadow Environment" token drift. This seems to be a discovery/registry failure. Any ideas?
Thanking you in advance for any assistance.
Solution
Yep, that’ll do it.
Fix is exactly what you said: install deps inside the plugin root (the directory that contains
On v2026, two notes:
- If you installed the plugin via
- After installing deps, do the Gateway restart again so the loader re-requires the module cleanly.
If you want an even more dependency-free fallback while testing, you can temporarily define
Fix is exactly what you said: install deps inside the plugin root (the directory that contains
openclaw.plugin.jsonindex.jsnode_modulesOn v2026, two notes:
- If you installed the plugin via
openclaw plugins install …npm install --ignore-scripts@sinclair/typebox- After installing deps, do the Gateway restart again so the loader re-requires the module cleanly.
If you want an even more dependency-free fallback while testing, you can temporarily define
parameterstypebox
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Was this page helpful?
