Repository navigation
Channel Plugins
Jazzen Chen edited this page May 24, 2026
·
6 revisions
Channel plugins connect messaging platforms to the local VibeAround runtime. They are standalone Node.js packages managed by the desktop app and runtime.
| Channel | Package style | Notes |
|---|---|---|
| Telegram | Bot token | Good personal mobile bot |
| Feishu / Lark | App credentials | Enterprise chat and rich cards |
| Discord | Bot token | Server channels and direct messages |
| Slack | Bot token + Socket Mode app token | Workspace messages and /va commands |
| OpenClaw-compatible QR login | Personal WeChat bridge | |
| DingTalk | Stream API credentials | Enterprise chat |
| WeCom | WebSocket bot credentials | Enterprise WeChat |
| QQ Bot | App ID and token | QQ guild bot workflows |
- VibeAround starts the plugin as a subprocess.
- Host and plugin communicate over stdio JSON-RPC.
- The plugin receives platform events and forwards prompts to VibeAround.
- VibeAround routes the prompt to the selected local agent/session.
- The plugin renders agent output back to the messaging platform.
Plugins adapt agent output to each platform:
- text blocks
- thinking blocks, when verbosity allows
- tool-use blocks, when verbosity allows
- attachments or files when the platform supports them
- streaming edits or send-only messages depending on platform capability
The desktop app can install channel plugins during onboarding or from Settings. Development checkouts can also run plugins from src/plugins/<name>.
Production user installs live under:
~/.vibearound/plugins/<plugin-id>/
Common commands:
/new
/switch codex
/switch claude
/handover
/pickup <code>
/profile
/agent
Slack uses /va because Slack reserves normal slash-command names:
/va switch codex
/va handover
Channels do not move execution to the messaging provider. They relay prompts to the local VibeAround runtime. The agent still runs on the user's machine with local permissions.
See Channel Configuration for credentials.
