Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
After upgrading to 5.2, the brave plugin cannot be installed via either stable or beta channel. The stable package (0.0.9) is missing openclaw.extensions in package.json, and brave@beta does not exist on npm. Users who had Brave configured before upgrading receive a stale config warn on every gateway startup with no way to restore the plugin.
Steps to reproduce
Upgrade to 2026.5.2
Run openclaw plugins install brave
Observe missing openclaw.extensions error
Run openclaw plugins install brave@beta
Observe package not found
Expected behavior
After upgrading to 5.2, openclaw plugins install brave should succeed. Release notes state Brave was externalized as a beta plugin, so either the stable or beta install path should work.
Actual behavior
openclaw plugins install brave
→ package.json missing openclaw.extensions; update the plugin package to include openclaw.extensions
openclaw plugins install brave@beta
→ Package not found on npm: brave@beta
Upgrade to 2026.5.2
Run openclaw plugins install brave
Observe missing openclaw.extensions error
Run openclaw plugins install brave@beta
Observe package not found
Note
The gateway logs a stale config warn on every startup:
plugins.entries.brave: plugin not found: brave (stale config entry ignored; remove it from plugins config)
Users who had Brave configured before upgrading to 5.2 cannot reinstall it. The brave@beta fallback mentioned in the release notes does not exist on npm.
OpenClaw version
2026.5.2 (8b2a6e5)
Operating system
Rocky Linux
Install method
openclaw update
Model
N/A — plugin packaging issue
Provider / routing chain
N/A — plugin packaging issue
Additional provider/model setup details
No response
Logs, screenshots, and evidence
**Logs**
`openclaw plugins install brave` (stable):
package.json missing openclaw.extensions; update the plugin package to include openclaw.extensions (for example ["./dist/index.js"])
Also not a valid hook pack: Error: package.json missing openclaw.hooks
`openclaw plugins install brave@beta`:
No matching version found for brave@beta.
error code ETARGET
notarget No matching version found for brave@beta.
node v24.14.1 / npm v11.11.0 / os Linux
Impact and severity
No response
Additional information
No response
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
After upgrading to 5.2, the brave plugin cannot be installed via either stable or beta channel. The stable package (0.0.9) is missing openclaw.extensions in package.json, and brave@beta does not exist on npm. Users who had Brave configured before upgrading receive a stale config warn on every gateway startup with no way to restore the plugin.
Steps to reproduce
Upgrade to 2026.5.2
Run openclaw plugins install brave
Observe missing openclaw.extensions error
Run openclaw plugins install brave@beta
Observe package not found
Expected behavior
After upgrading to 5.2,
openclaw plugins install braveshould succeed. Release notes state Brave was externalized as a beta plugin, so either the stable or beta install path should work.Actual behavior
openclaw plugins install brave
→ package.json missing openclaw.extensions; update the plugin package to include openclaw.extensions
openclaw plugins install brave@beta
→ Package not found on npm: brave@beta
Upgrade to 2026.5.2
Run openclaw plugins install brave
Observe missing openclaw.extensions error
Run openclaw plugins install brave@beta
Observe package not found
Note
The gateway logs a stale config warn on every startup:
plugins.entries.brave: plugin not found: brave (stale config entry ignored; remove it from plugins config)
Users who had Brave configured before upgrading to 5.2 cannot reinstall it. The brave@beta fallback mentioned in the release notes does not exist on npm.
OpenClaw version
2026.5.2 (8b2a6e5)
Operating system
Rocky Linux
Install method
openclaw update
Model
N/A — plugin packaging issue
Provider / routing chain
N/A — plugin packaging issue
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response