feat: use Web Speech API for voice transcription #149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Replace the broken server-side OpenAI Whisper transcription with the browser-native Web Speech API.
Problem
The microphone button in the chat input was calling
/api/speech-to-textwhich no longer exists. The original API endpoint was removed in commit c4200ec9 ("Remove all legacy Blink v1 code") but the microphone button UI was kept, causing all transcription attempts to fail with "Speech transcription failed. Please try again."Solution
Instead of re-adding the server-side OpenAI Whisper integration, this PR uses the browser-native Web Speech API (
SpeechRecognition) which:Changes
MediaRecorder-based audio capture and/api/speech-to-textfetch callSpeechRecognitionAPI for real-time transcriptionisTranscribingstate since transcription happens in real-timeBrowser Support
On unsupported browsers, the microphone button is hidden rather than showing a broken feature.
Testing
Related
Slack thread: Investigation into why voice transcription was failing