docs/plugins/community.md
Community plugins are third-party packages that extend OpenClaw with new channels, tools, providers, or other capabilities. They are built and maintained by the community, usually published on ClawHub, and installable with a single command. Npm remains the launch default for bare package specs while ClawHub pack installs roll out.
ClawHub is the canonical discovery surface for community plugins. Do not open docs-only PRs just to add your plugin here for discoverability; publish it on ClawHub instead.
openclaw plugins install clawhub:<package-name>
Use openclaw plugins install <package-name> for npm-hosted packages.
Scrape data from any website with 20,000+ ready-made scrapers. Let your agent extract data from Instagram, Facebook, TikTok, YouTube, Google Maps, Google Search, e-commerce sites, and more — just by asking.
@apify/apify-openclaw-pluginopenclaw plugins install @apify/apify-openclaw-plugin
Independent OpenClaw bridge for Codex App Server conversations. Bind a chat to a Codex thread, talk to it with plain text, and control it with chat-native commands for resume, planning, review, model selection, compaction, and more.
openclaw-codex-app-serveropenclaw plugins install openclaw-codex-app-server
Enterprise robot integration using Stream mode. Supports text, images, and file messages via any DingTalk client.
@largezhou/ddingtalkopenclaw plugins install @largezhou/ddingtalk
Lossless Context Management plugin for OpenClaw. DAG-based conversation summarization with incremental compaction — preserves full context fidelity while reducing token usage.
@martian-engineering/lossless-clawopenclaw plugins install @martian-engineering/lossless-claw
Official plugin that exports agent traces to Opik. Monitor agent behavior, cost, tokens, errors, and more.
@opik/opik-openclawopenclaw plugins install @opik/opik-openclaw
Give your OpenClaw agent a Live2D avatar with real-time lip-sync, emotion expressions, and text-to-speech. Includes creator tools for AI asset generation and one-click deployment to the Prometheus Marketplace. Currently in alpha.
@prometheusavatar/openclaw-pluginopenclaw plugins install @prometheusavatar/openclaw-plugin
Connect OpenClaw to QQ via the QQ Bot API. Supports private chats, group mentions, channel messages, and rich media including voice, images, videos, and files.
Current OpenClaw releases bundle QQ Bot. Use the bundled setup in QQ Bot for normal installs; install this external plugin only when you intentionally want the Tencent-maintained standalone package.
@tencent-connect/openclaw-qqbotopenclaw plugins install @tencent-connect/openclaw-qqbot
WeCom channel plugin for OpenClaw by the Tencent WeCom team. Powered by WeCom Bot WebSocket persistent connections, it supports direct messages & group chats, streaming replies, proactive messaging, image/file processing, Markdown formatting, built-in access control, and document/meeting/messaging skills.
@wecom/wecom-openclaw-pluginopenclaw plugins install @wecom/wecom-openclaw-plugin
Yuanbao channel plugin for OpenClaw by the Tencent Yuanbao team. Powered by WebSocket persistent connections, it supports direct messages & group chats, streaming replies, proactive messaging, image/file/audio/video processing, Markdown formatting, built-in access control, and slash-command menus.
openclaw-plugin-yuanbaoopenclaw plugins install openclaw-plugin-yuanbao
We welcome community plugins that are useful, documented, and safe to operate.
<Steps> <Step title="Publish to ClawHub or npm"> Your plugin must be installable via `openclaw plugins install \<package-name\>`. Publish to [ClawHub](/tools/clawhub) unless you specifically need npm-only distribution. See [Building Plugins](/plugins/building-plugins) for the full guide. </Step> <Step title="Host on GitHub"> Source code must be in a public repository with setup docs and an issue tracker. </Step> <Step title="Use docs PRs only for source-doc changes"> You do not need a docs PR just to make your plugin discoverable. Publish it on ClawHub instead.Open a docs PR only when OpenClaw's source docs need an actual content
change, such as correcting install guidance or adding cross-repo
documentation that belongs in the main docs set.
| Requirement | Why |
|---|---|
| Published on ClawHub or npm | Users need openclaw plugins install 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 |
Low-effort wrappers, unclear ownership, or unmaintained packages may be declined.