Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

turnComplete: false in ClientContentMessage prevents later response to RealtimeInputMessages #60

Open
romankupkovic opened this issue Jan 25, 2025 · 0 comments

Comments

@romankupkovic
Copy link

Description of the bug:

I want to send contextual text data using the ClientContentMessage to the API while being connected and talking to the model using RealtimeInputMessages but the API should not generate a response to the context data so I set turnCompleteto false.

After sending the ClientContentMessage with the text data, I get no response, as expected, but further RealtimeInputMessages that are recorded and logged also do not trigger a response anymore, even If I want to continue the voice conversation.

Image

Actual vs expected behavior:

Actual behaviour: RealtimeInputMessage after the ClientContentMessage with turnComplete set to falsedoes not trigger API response.

Expected Behaviour: RealtimeInputMessage after the ClientContentMessage with turnComplete set to falsedoes trigger API response.

Any other information you'd like to share?

I could not find any mention of this dynamic in the documentation or forums.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant