openclaw - 💡(How to fix) Fix Voice wake mode should respect selected session target in macOS app [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#51040Fetched 2026-04-08 01:05:11
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Participants
Timeline (top)
commented ×1

When using voice wake mode on the macOS node app, responses always route to the main webchat session regardless of which session target is selected in the app's dropdown.

Root Cause

When using voice wake mode on the macOS node app, responses always route to the main webchat session regardless of which session target is selected in the app's dropdown.

RAW_BUFFERClick to expand / collapse

Description

When using voice wake mode on the macOS node app, responses always route to the main webchat session regardless of which session target is selected in the app's dropdown.

Expected Behavior

Voice wake responses should route to whatever session the user has selected in the macOS app's session picker (e.g., a specific Telegram group).

Current Behavior

Voice wake always routes to the webchat session, ignoring the dropdown selection.

Steps to Reproduce

  1. Open the macOS node app
  2. Select a non-webchat session target from the dropdown (e.g., a Telegram group)
  3. Trigger voice wake mode
  4. Response arrives in webchat instead of the selected session

Environment

  • OpenClaw: 2026.3.13
  • macOS node app
  • Node: openclaw-macos (Jeff's Mac Studio)

extent analysis

Fix Plan

The fix involves updating the session routing logic in the voice wake mode to respect the user's selected session target.

Steps to Fix

  • Update the voiceWakeHandler function to retrieve the currently selected session target from the app's state.
  • Modify the routeResponse function to use the selected session target instead of defaulting to the webchat session.

Example Code

// Get the currently selected session target
const selectedSession = appState.getSessionTarget();

// Update the routeResponse function
function routeResponse(response) {
  // ...
  const targetSession = selectedSession; // Use the selected session target
  // ...
  targetSession.sendResponse(response);
}

Verification

  1. Open the macOS node app.
  2. Select a non-webchat session target from the dropdown.
  3. Trigger voice wake mode.
  4. Verify that the response arrives in the selected session.

Extra Tips

  • Ensure that the appState.getSessionTarget() function returns the correct session target.
  • Test the fix with different session targets to ensure the routing logic works as expected.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Voice wake mode should respect selected session target in macOS app [1 comments, 2 participants]