PR #64531: fix(bluebubbles): add configurable outbound send method

• Repository: openclaw/openclaw
• Author: Lucenx9
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/64531

Description (problem / solution / changelog)

Summary

• Problem: BlueBubbles config did not expose the upstream method send option, so users could not force apple-script or private-api for outbound sends when their server/setup required it.
• Why it matters: issue #64480 reports real deployments where OpenClaw needs an explicit AppleScript send path instead of only the current automatic behavior.
• What changed: added sendMethod to the BlueBubbles config contract, normalized it in account resolution, applied it to text/new-chat/attachment sends, and documented the option.
• What did NOT change (scope boundary): default behavior is unchanged when sendMethod is unset, and Private API still takes precedence when reply/effect/private-only delivery paths require it.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #64480
• Related #
• This PR fixes a bug or regression

Root Cause (if applicable)

• Root cause: the BlueBubbles config/schema surface did not expose the upstream send method, even though BlueBubbles Server supports apple-script and private-api for outbound delivery.
• Missing detection / guardrail: there was no regression coverage for honoring a configured send method on text and attachment sends.
• Contributing context (if known): previous BlueBubbles fixes focused on forcing private-api when available, but not on exposing a user-configurable override for environments where Private API is unavailable or undesired.

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file: extensions/bluebubbles/src/send.test.ts, extensions/bluebubbles/src/attachments.test.ts
• Scenario the test should lock in: configured sendMethod: "apple-script" is forwarded for normal text sends, new-chat creation sends, and attachment sends, while private-api-only reply behavior still prefers private-api.
• Why this is the smallest reliable guardrail: the regression is isolated to BlueBubbles payload construction and account resolution, so extension-local send tests catch it directly.
• Existing test that already covers this (if any): N/A
• If no new test is added, why not: N/A

User-visible / Behavior Changes

• New optional config: channels.bluebubbles.sendMethod with supported values apple-script and private-api.
• The same override also works on BlueBubbles accounts through the account config surface.
• Leaving the field unset preserves current behavior.

Diagram (if applicable)

Before:
[user config] -> [BlueBubbles send] -> [OpenClaw default method selection only]

After:
[user config sendMethod] -> [BlueBubbles send/account resolution] -> [configured method unless private-api-only path requires private-api]

Security Impact (required)

• New permissions/capabilities? (No)
• Secrets/tokens handling changed? (No)
• New/changed network calls? (No)
• Command/tool execution surface changed? (No)
• Data access scope changed? (No)
• If any Yes, explain risk + mitigation:

Repro + Verification

Environment

• OS: Linux local dev host
• Runtime/container: Node 22 + pnpm
• Model/provider: N/A
• Integration/channel (if any): BlueBubbles
• Relevant config (redacted): BlueBubbles server URL/password with optional channels.bluebubbles.sendMethod

Steps

1. Configure BlueBubbles with sendMethod: "apple-script".
2. Send a normal text message, an attachment, or create a new chat through the BlueBubbles extension.
3. Inspect the outbound BlueBubbles request payload.

Expected

• The outbound payload includes the configured method unless the send path requires private-api for reply/effect/private-only behavior.

Actual

• Before this change, there was no config surface to express the send method override.

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

• Verified scenarios:
  • pnpm test:extension bluebubbles
  • pnpm test extensions/bluebubbles/src/send.test.ts extensions/bluebubbles/src/attachments.test.ts
  • pnpm config:channels:gen
  • pnpm config:channels:check
  • pnpm config:docs:gen
  • pnpm config:docs:check
• Edge cases checked:
  • explicit apple-script for plain sends
  • explicit apple-script for chat creation path
  • attachment sends honor configured method
  • private-api reply threading still prefers private-api
• What you did not verify:
  • live end-to-end delivery against a real BlueBubbles server
  • full repo-wide pnpm check is currently blocked by pre-existing await-thenable lint failures in untouched files already present on origin/main

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? (Yes)
• Config/env changes? (Yes)
• Migration needed? (No)
• If yes, exact upgrade steps:
  • Optional only: set channels.bluebubbles.sendMethod (or the per-account equivalent) if you need to override OpenClaw's default BlueBubbles send method.

Risks and Mitigations

• Risk: a user can configure private-api on a server where Private API is unavailable.
  • Mitigation: the option is explicit/optional, default behavior stays unchanged, and existing BlueBubbles server behavior remains the enforcement point.
• Risk: reviewers may interpret the repo-wide pnpm check red state as caused by this diff.
  • Mitigation: extension-local tests and config/doc generation checks are included above, and the failing lint lines are unchanged from current origin/main.

AI-assisted: Yes (Codex) Testing level: Targeted extension lane + config/doc generation checks

Changed files

• docs/.generated/config-baseline.sha256 (modified, +2/-2)
• docs/channels/bluebubbles.md (modified, +1/-0)
• extensions/bluebubbles/src/account-resolve.ts (modified, +6/-0)
• extensions/bluebubbles/src/attachments.test.ts (modified, +71/-0)
• extensions/bluebubbles/src/attachments.ts (modified, +8/-4)
• extensions/bluebubbles/src/config-schema.ts (modified, +3/-0)
• extensions/bluebubbles/src/config-ui-hints.ts (modified, +4/-0)
• extensions/bluebubbles/src/send.test.ts (modified, +71/-0)
• extensions/bluebubbles/src/send.ts (modified, +18/-8)
• extensions/bluebubbles/src/types.ts (modified, +60/-27)
• src/config/bundled-channel-config-metadata.generated.ts (modified, +12/-0)
• src/config/zod-schema.providers-core.ts (modified, +1/-0)

PR #64550: fix(bluebubbles): set apple-script send method when Private API is unavailable

• Repository: openclaw/openclaw
• Author: Yanhu007
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/64550

Description (problem / solution / changelog)

Summary

Fixes #64480 — BlueBubbles messages silently fail to deliver when Private API is not enabled.

Root Cause

The sendMessageBlueBubbles() function only sets payload.method when Private API is available:

if (privateApiDecision.canUsePrivateApi) {
    payload.method = "private-api";
}
// Otherwise: no method field at all

The BlueBubbles server API requires an explicit send method. Without it, the message enters Messages.app on the Mac but is never actually sent to the recipient — BlueBubbles reports "delivered" but the message shows "Not Delivered" on the device.

Fix

Add method: "apple-script" as the fallback when Private API is not available. This is the standard send mechanism for macOS setups with SIP enabled.

Verification

The reporter confirmed that curl with "method": "apple-script" delivers successfully every time.

Changed files

• extensions/bluebubbles/src/send.test.ts (modified, +3/-3)
• extensions/bluebubbles/src/send.ts (modified, +5/-0)
• extensions/browser/src/browser/chrome.ts (modified, +6/-0)
• src/auto-reply/reply/reply-media-paths.ts (modified, +13/-0)