Skip to main content

Community Plugins

Community plugins are third-party packages that extend Velaclaw with new channels, tools, providers, or other capabilities. They are built and maintained by the community, published on ClawHub or npm, and installable with a single command. 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.
Velaclaw checks ClawHub first and falls back to npm automatically.

Listed plugins

Codex App Server Bridge

Independent Velaclaw 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.

DingTalk

Enterprise robot integration using Stream mode. Supports text, images, and file messages via any DingTalk client.

Lossless Claw (LCM)

Lossless Context Management plugin for Velaclaw. DAG-based conversation summarization with incremental compaction — preserves full context fidelity while reducing token usage.

Opik

Official plugin that exports agent traces to Opik. Monitor agent behavior, cost, tokens, errors, and more.

QQbot

Connect Velaclaw to QQ via the QQ Bot API. Supports private chats, group mentions, channel messages, and rich media including voice, images, videos, and files.

wecom

WeCom channel plugin for Velaclaw 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.

Submit your plugin

We welcome community plugins that are useful, documented, and safe to operate.
1

Publish to ClawHub or npm

Your plugin must be installable via velaclaw plugins install \<package-name\>. Publish to ClawHub (preferred) or npm. See Building Plugins for the full guide.
2

Host on GitHub

Source code must be in a public repository with setup docs and an issue tracker.
3

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 Velaclaw’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.

Quality bar

Low-effort wrappers, unclear ownership, or unmaintained packages may be declined.