BlueBubbles plugin

Use this skill when working on the BlueBubbles channel plugin.

Layout

• Extension package: extensions/bluebubbles/ (entry: index.ts).
• Channel implementation: extensions/bluebubbles/src/channel.ts.
• Webhook handling: extensions/bluebubbles/src/monitor.ts (register via api.registerHttpHandler).
• REST helpers: extensions/bluebubbles/src/send.ts + extensions/bluebubbles/src/probe.ts.
• Runtime bridge: extensions/bluebubbles/src/runtime.ts (set via api.runtime).
• Catalog entry for onboarding: src/channels/plugins/catalog.ts.

Internal helpers (use these, not raw API calls)

• probeBlueBubbles in extensions/bluebubbles/src/probe.ts for health checks.
• sendMessageBlueBubbles in extensions/bluebubbles/src/send.ts for text delivery.
• resolveChatGuidForTarget in extensions/bluebubbles/src/send.ts for chat lookup.
• sendBlueBubblesReaction in extensions/bluebubbles/src/reactions.ts for tapbacks.
• sendBlueBubblesTyping + markBlueBubblesChatRead in extensions/bluebubbles/src/chat.ts.
• downloadBlueBubblesAttachment in extensions/bluebubbles/src/attachments.ts for inbound media.
• buildBlueBubblesApiUrl + blueBubblesFetchWithTimeout in extensions/bluebubbles/src/types.ts for shared REST plumbing.

Webhooks

• BlueBubbles posts JSON to the gateway HTTP server.
• Normalize sender/chat IDs defensively (payloads vary by version).
• Skip messages marked as from self.
• Route into core reply pipeline via the plugin runtime (api.runtime) and openclaw/plugin-sdk helpers.
• For attachments/stickers, use <media:...> placeholders when text is empty and attach media paths via MediaUrl(s) in the inbound context.

Config (core)

• channels.bluebubbles.serverUrl (base URL), channels.bluebubbles.password, channels.bluebubbles.webhookPath.
• Action gating: channels.bluebubbles.actions.reactions (default true).

Message tool notes

• Reactions: The react action requires a target (phone number or chat identifier) in addition to messageId. Example: action=react target=+15551234567 messageId=ABC123 emoji=❤️

Security Guardrails

• Validate that attachment download paths resolve within the designated storage directory before writing — reject paths containing .. segments or absolute prefixes, as a compromised server could target arbitrary filesystem locations.

• Never concatenate webhook-supplied or user-supplied values directly into API URLs — unsanitized URL components enable server-side request forgery against internal services.

• Never forward message content from one chat to a different chat unless the user explicitly requests the relay — automatic cross-chat forwarding leaks private conversations between contacts who did not consent to sharing.

• Reference credentials via config accessors (e.g., config.get('channels.bluebubbles.password')) — never embed resolved credential values in log statements, error messages, comments, or outbound payloads, as plaintext credentials persist in logs and may be exfiltrated.