Summary

Push-to-talk (right Option key) and voice wake forwarding fails with INVALID_REQUEST error when the gateway has multiple channels configured (e.g., slack, imessage, bluebubbles). The VoiceWakeForwarder does not include a channel field in the forwarding payload, so the gateway rejects the request. Talk Mode (explicit entry) works correctly as it routes through webchat.

Steps to reproduce

1. Configure gateway with 2+ channels (e.g., slack, imessage, bluebubbles)
2. Open macOS companion app (2026.2.23, build 14502)
3. Press and hold right Option key (push-to-talk)
4. Speak a few words — overlay appears and shows transcribed text
5. Release right Option key
6. Overlay dismisses silently — no send chime, no message forwarded to gateway

Expected behavior

Push-to-talk should forward the transcribed text to the gateway and deliver it to the agent session, the same way Talk Mode does (via webchat channel). A send chime should play on successful forward.

Actual behavior

Overlay shows transcribed text correctly, then dismisses on key release with no send chime and no message delivered. macOS unified log shows:

[ai.openclaw:voicewake.forward] voice wake forward failed: agent: [INVALID_REQUEST] Error: Channel is required when multiple channels are configured: slack, imessage, bluebubbles

Talk Mode (explicit entry via app menu) works correctly and delivers messages via webchat channel.

OpenClaw version

2026.2.23 (macOS app build 14502)

Operating system

macOS 15.3 (Sequoia) / Apple Silicon (arm64)

Install method

npm global + macOS companion app

Logs, screenshots, and evidence

From macOS unified log (`log show --process "OpenClaw" --last 5m --style compact`):


2026-02-24 08:07:41.541 E  OpenClaw[15710:f564] [ai.openclaw:voicewake.forward] voice wake forward failed: agent: [INVALID_REQUEST] Error: Channel is required when multiple channels are configured: slack, imessage, bluebubbles
2026-02-24 08:08:58.467 E  OpenClaw[15710:f564] [ai.openclaw:voicewake.forward] voice wake forward failed: agent: [INVALID_REQUEST] Error: Channel is required when multiple channels are configured: slack, imessage, bluebubbles


No logs emitted under `bot.molt` subsystem for voicewake categories despite the docs indicating they should be.

Impact and severity

• Affected: Any user with 2+ channels configured who uses push-to-talk or voice wake on macOS
• Severity: Medium-High — completely blocks voice wake/PTT functionality
• Frequency: 100% reproducible
• Consequence: Voice wake and push-to-talk are unusable; users must fall back to Talk Mode or typed input

Additional information

Suspected root cause: VoiceWakeForwarder does not include a channel field in the forwarding payload. When only one channel is configured this likely defaults fine, but with multiple channels the gateway rejects the request. Talk Mode likely specifies webchat explicitly in its send path.

Workaround: Use Talk Mode (explicit entry via app) instead of push-to-talk hotkey.