claude-code - 💡(How to fix) Fix [Claude Code tab] Split-view voice-mode toggle plays sound cue but fails to activate mic [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
anthropics/claude-code#48450Fetched 2026-04-16 06:59:49
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

In Claude Desktop's Claude Code tab, the new split-view feature allows toggling voice mode, but the toggle plays the "voice starting" audio cue without actually activating the microphone. Voice input never captures.

Root Cause

In Claude Desktop's Claude Code tab, the new split-view feature allows toggling voice mode, but the toggle plays the "voice starting" audio cue without actually activating the microphone. Voice input never captures.

RAW_BUFFERClick to expand / collapse

Summary

In Claude Desktop's Claude Code tab, the new split-view feature allows toggling voice mode, but the toggle plays the "voice starting" audio cue without actually activating the microphone. Voice input never captures.

Steps to reproduce

  1. Open Claude Desktop, Claude Code tab
  2. Enable split view (two sessions visible side by side)
  3. Click into one of the session panes to give it focus
  4. Toggle voice mode (shortcut or UI button)

Expected behavior

Voice mode activates on the focused session pane. Microphone opens. Voice input is captured and transcribed into that session's input field.

Actual behavior

The "voice mode starting" audio cue plays — but microphone never opens and voice mode does not actually engage. The sound cue fires independently of whether the toggle succeeded.

Suspected cause

The voice-toggle handler may not be scoping the action to the recently-clicked (focused) pane in split view. Toggle event fires but binds to the wrong or a null target session.

Environment

  • OS: Windows 11
  • Claude Code: 2.1.108
  • Feature: Claude Code tab in Claude Desktop, new split-view mode

extent analysis

TL;DR

The issue can likely be resolved by ensuring the voice-toggle handler correctly scopes the action to the focused session pane in split-view mode.

Guidance

  • Verify that the voice-toggle handler is correctly binding to the focused session pane by checking the event target and ensuring it matches the expected pane.
  • Inspect the code to confirm that the toggle event is being handled within the context of the focused session pane, rather than a parent or unrelated element.
  • Consider adding logging or debugging statements to the voice-toggle handler to confirm the target element and verify that the microphone is being activated as expected.
  • Review the split-view mode implementation to ensure that the focused session pane is being properly tracked and updated when the user interacts with the UI.

Example

// Pseudocode example, actual implementation may vary
const focusedPane = getFocusedSessionPane();
if (focusedPane) {
  // Activate voice mode on the focused pane
  focusedPane.activateVoiceMode();
} else {
  // Handle case where no pane is focused
  console.error("No session pane is focused");
}

Notes

The provided information suggests that the issue is related to the voice-toggle handler not scoping the action to the correct session pane. However, without access to the actual codebase, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Modify the voice-toggle handler to correctly scope the action to the focused session pane, as described in the guidance section. This should resolve the issue and allow voice mode to function as expected in split-view mode.

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…

FAQ

Expected behavior

Voice mode activates on the focused session pane. Microphone opens. Voice input is captured and transcribed into that session's input field.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING