Repository navigation
Telegram voice messages are transcribed and reach the agent as text - #151
Merged
Merged
Conversation
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
Voice messages (and round video messages) sent to a Telegram bot used to reach the agent only as an attached
.oggfile. Now Godmode transcribes them first and the words become the message. The recording stays attached.Tests
voice.test.ts: key order, API tool keys and their scope, exact host match, empty and oversized recordings, provider errors.messaging.test.ts: voice message without a key, with a key, silent recording with a caption, spoken slash, provider refusal, spoken approval and an unheard answer.Slack and Teams are unchanged.