[BUG] Voice dictation sends transcription to both panes in Claude Code Desktop split view
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
What's Wrong?
When using split view in the Claude Code Desktop app on Windows (two sessions open side by side), pressing the in-app microphone button captures voice and sends the transcribed text to the input fields of both panes simultaneously — not just the one where the mic button was clicked.
What Should Happen?
Expected Behavior
Voice dictation should only send transcribed text to the input field of the pane where the mic button was clicked.
Error Messages/Logs
Steps to Reproduce
Steps to Reproduce
Open Claude Code Desktop app
Open split view with two separate sessions/projects side by side
Click the microphone button in one of the two panes
Speak a prompt
Observe that the transcribed text appears in the input fields of both panes
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.112
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
Actual Behavior
Both split view panes receive the transcription, regardless of which pane initiated the recording. This makes it impossible to use voice input in split view, as unrelated prompts get injected into the wrong session.
Environment
- OS: Windows
- Model: Opus 4.6
- App: Claude Code Desktop (split view)
Additional Context
This appears to be a shared dictation handler issue — the transcription stream isn't scoped to the originating pane. Using Windows native voice typing (Win + H) does not have this problem since it respects input focus.
Screenshot showing both windows receiving the same voice input:
<img width="778" height="165" alt="Image" src="https://github.com/user-attachments/assets/990d91d2-bd6e-4680-b8b0-ecc642a36586" />
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗