What breaks without openclaw plugin registry
Untested plugins breaking installs. No version compatibility metadata. Hours finding the right package.
→
Verified plugin discovery × curated compatibility metadata ÷ 5-minute browse ÷ zero broken installs = the right plugin, first try.
Security check — openclaw plugin registry
Privacy score: 7/10 — accesses connected platform APIs only.
Lock it: review OAuth scopes before install, confirm Linux, macOS, Windows (WSL); OpenClaw ≥1.2 compatibility.
Quick start — openclaw plugin registry in 5 minutes
Setup time: 5 minutes
!
You need:
- OpenClaw core installed
- Node.js ≥18
Install the package:
npm install @openclaw/clawhub
1
Install the clawhub plugin via npm
2
Add to openclaw.config.js plugins array
3
Restart OpenClaw — a /clawhub command becomes available
4
Use openclaw plugin search <name> from CLI to find plugins
5
Install found plugin with openclaw plugin install <name>
Compatibility & status
Works with: Linux, macOS, Windows (WSL); OpenClaw ≥1.2
beginner
Last updated: Oct 2025
★ 620 on GitHub
MIT
Official docs →
View on GitHub →
FAQ — openclaw plugin registry
Is ClawHub the same as the npm registry?
No. ClawHub is a metadata and discovery layer on top of npm, adding trust signals and categories.
Can I submit my own plugin?
Yes. Open a PR to the clawhub repo with your plugin's metadata YAML file.
Does ClawHub work offline?
CLI tool caches the last-fetched registry locally for basic search, but install requires npm access.
Every broken plugin install wastes an hour of debugging time you didn't budget.
Without metadata, you discover compatibility failures in production.
Get it on GitHub →