d6d7435f59
* feat(plugins): default unprefixed packages to ClawHub Use the shared source planner for CLI, chat, and assistant installs. Keep explicit npm and local sources, preserve canonical built-in shortcuts, and retain the selected registry in update and repair records. Autoreview findings addressed: - [P2] Preserve ClawHub provenance in search hints that match aliases Route scoped packages through ClawHub and add @latest to ambiguous unscoped search hints. - [P2] Preserve usable search hints for scoped names with file suffixes Treat file-suffixed package names as registry specs, migrate source-selection tests, and retain npm in retry guidance. - [P2] Update the remaining source-selection test expectations Treat file-suffixed package names as registry specs, migrate source-selection tests, and retain npm in retry guidance. - [P2] Keep npm prerelease retry hints on npm Treat file-suffixed package names as registry specs, migrate source-selection tests, and retain npm in retry guidance. - [P2] Restrict catalog shortcuts to canonical plugin IDs Restrict bare shortcuts to canonical IDs and retain npm in shared hook-pack prerelease guidance. - [P2] Preserve npm in hook-pack prerelease guidance Restrict bare shortcuts to canonical IDs and retain npm in shared hook-pack prerelease guidance. * docs(plugins): show ClawHub as the default install source Update setup examples and generated inventory instructions to omit the ClawHub prefix. Document explicit npm selection and canonical plugin-ID shortcuts. * fix(plugins): keep recovery tied to the selected source * test(plugins): cover search commands and saved registry choices * test(plugins): align pre-action recovery with selected sources * test(plugins): prove source-bound recovery through the CLI * fix(plugins): retain official identity during config recovery
2.7 KiB
| summary | read_when | title | doc-schema-version | ||
|---|---|---|---|---|---|
| Find and publish community-maintained OpenClaw plugins |
|
Community plugins | 1 |
Community plugins are third-party packages that extend OpenClaw with channels, tools, providers, hooks, or other capabilities. Use ClawHub as the primary discovery surface for public community plugins.
Find plugins
Search ClawHub from the CLI:
openclaw plugins search "calendar"
Install a ClawHub plugin with an explicit source prefix:
openclaw plugins install <package-name>
npm remains a supported direct-install path:
openclaw plugins install npm:<package-name>
Use Manage plugins for common install, update,
inspect, and uninstall examples. Use openclaw plugins for
the full command reference and source-selection rules.
Publish plugins
Publish public community plugins on ClawHub so OpenClaw users can discover and install them. ClawHub owns the live package listing, release history, scan status, and install hints; the docs do not maintain a static third-party plugin catalog.
clawhub package publish your-org/your-plugin --dry-run
clawhub package publish your-org/your-plugin
Before publishing, make sure the plugin has package metadata, a plugin manifest, setup docs, and a clear maintenance owner. ClawHub validates owner scope, package name, version, file limits, and source metadata before creating a release, then keeps new releases hidden from normal install and download surfaces until review and verification finish.
Checklist before you publish:
| Requirement | Why |
|---|---|
| Published on ClawHub | Users need openclaw plugins install hints to work |
| Public GitHub repo | Source review, issue tracking, transparency |
| Setup and usage docs | Users need to know how to configure it |
| Active maintenance | Recent updates or responsive issue handling |
Full publishing contract:
- ClawHub publishing - owners, scopes, releases, review, package validation, and package transfer
- Building plugins - the plugin package shape and first publish workflow
- Plugin manifest - native plugin manifest fields
Related
- Plugins - install, configure, reload, and troubleshoot
- Manage plugins - command examples
- ClawHub publishing - publish and release rules