#plugins on clawhub
1 messages · Page 1 of 1 (latest)
Yep, for code plugins published to ClawHub the expected format is:
"openclaw": {
"compat": {
"pluginApi": ">=2026.4.11"
},
"build": {
"openclawVersion": "2026.4.11"
}
}
So, exactly:
openclaw.compat.pluginApi- semver range string
-
normally
>=<openclaw-version>- examples:
">=2026.4.11"">=2026.3.24-beta.2"
- examples:
-
openclaw.build.openclawVersion- exact version string
- no range operator
- examples:
"2026.4.11""2026.3.24-beta.2"
I'd stick to the bare version form, no v prefix.
The docs/examples match that exactly: