Restore Ava voice and add Indian-English support - #27
Merged
Conversation
added 7 commits
August 13, 2026 16:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
Why
Production voice stopped before transcription because Nova-3 did not establish the WebSocket expected by the full
withVoicepipeline. Cloudflare currently recommends Flux STT for conversational voice agents. Cloudflare-hosted TTS does not expose an Indian-English speaker, so the optional Indian voice uses Deepgram Flux TTS while retaining a Cloudflare-hosted PCM fallback.Validation
npm run checknpm run eval:voice(full pass on rerun; first run exposed one nondeterministic ticket-intake response)npm auditandnpm audit --omit=dev— zero known vulnerabilities