Repository navigation
Add output_type to the RTVI bot-output message - #6351
Merged
Merged
Conversation
output_type says what kind of text a bot-output message holds, the bot's counterpart of input_type on user-input. text_type, which carries the same value, is deprecated alongside aggregated_by. The bot sends all three until 2.0.0, and pipecat eval reads output_type to find bot backchannels.
Codecov Report✅ All modified and coverable lines are covered by tests.
... and 7 files with indirect coverage changes 🚀 New features to boost your workflow:
|
markbackman
approved these changes
Oct 23, 2026
markbackman
left a comment
markbackman
left a comment
Contributor
There was a problem hiding this comment.
It's a bummer to make this change after we just made it, but I think it's the right call.
Contributor
Author
Yep, I realized after I saw |
mattieruth
pushed a commit
to pipecat-ai/pipecat-client-web
that referenced
this pull request
Oct 25, 2026
Pipecat's bot-output message now carries output_type, the counterpart of user-input's input_type (pipecat-ai/pipecat#6351). Fill in output_type, text_type and aggregated_by from whichever one the bot sends.
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.
The RTVI
bot-outputmessage says what kind of text it holds intext_type: a sentence, a word, a backchannel, or a custom type such ascode. Its user-side counterpart,user-input, calls the same ideainput_type. This addsoutput_typetobot-outputso the two messages match, and deprecatestext_type.output_type,text_typeandaggregated_bywith the same value until 2.0.0, so existing clients keep working. There's no protocol bump, as whentext_typewas added.BotOutputMessageData.output_typeis the required field. Setting any of the three names fills in the other two.TextType,skip_text_typesand the text transforms keeptext_type.pipecat evalreadsoutput_typeto find bot backchannels, so it won't see them from a 1.13 bot.