openclaw - 💡(How to fix) Fix sendAnnounce queue path passes deliver:true without channel for sessions with no origin [1 participants]

Bug

When the gateway has multiple channels configured (e.g., telegram + bluebubbles), the sendAnnounce function in the announce queue path (src/agents/subagent-announce-delivery.ts) unconditionally sets deliver: !requesterIsSubagent.

For Paperclip adapter sessions (agent:eng:paperclip:issue:*), which have channel: null, lastChannel: null, origin: null in the session store and subagent depth 0, this sends deliver: true with no explicit channel to the gateway's agent handler. The agent handler then hits resolveMessageChannelSelection which throws:

Channel is required when multiple channels are configured: telegram, bluebubbles

This causes ACP/subagent completion announcements to silently fail after exhausting retries (7 attempts observed).

Root Cause

The sendAnnounce function (queue drain path) doesn't check if the origin has a valid channel+to before setting deliver: true:

deliver: !requesterIsSubagent,  // Always true for depth-0 non-cron sessions

The direct path (sendSubagentAnnounceDirectly) correctly uses resolveExternalBestEffortDeliveryTarget which sets deliver: false when no channel+to pair exists.

Affected Versions

Confirmed in 2026.3.31 and 2026.4.1.

Suggested Fix

In sendAnnounce, gate deliver: true on the presence of a valid channel+to in the origin:

deliver: !requesterIsSubagent && Boolean(origin?.channel && origin?.to),
bestEffortDeliver: !requesterIsSubagent && !Boolean(origin?.channel && origin?.to),

This aligns the queue path behavior with the direct path's use of resolveExternalBestEffortDeliveryTarget.

Workaround

Local patch applied to dist/pi-embedded-iRgRpYxO.js as described in the suggested fix above. Will be overwritten on next npm update.