-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New Feature Proposal: Assistant API - Chaining streams for function execution #1261
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
Closed
1 task done
Comments
great workaround! Something like this is necessary since there could be an arbitrary number of tool_calls. |
Thanks for the suggestion! We have another, similar proposal in the works – stay tuned :) |
Hey @rattrayalex, could you share this proposal you mentioned? |
stainless-app bot
pushed a commit
that referenced
this issue
Mar 27, 2025
This reverts commit dd4af939792583854a313367c5fe2f98eea2f3c8.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Confirm this is a feature request for the Python library and not the underlying OpenAI API.
Describe the feature or improvement you're requesting
Hi,
I have developed a monkey patch to add the capacity for chaining streams which is very beneficial for the Assistant API function execution workflow. I think it could be integrated into the openai library. So, I guess you want to know the use case, right?
Imagine you are processing the assistant events in a loop (in my case I use the Async stream client but it's basically the almost same for the non-async streaming one):
With this, we can chain the tool submit stream response to the current one to avoid writing another chunk processing loop.
Tested & working.
It very beneficial, especially when you integrate the assistant API inside a project to avoid changing the existing workflow.
Here is the monkey patch:
Best regards,
Paul Irolla
Additional context
I have implemented this inside my personal fork of LiteLLM for integrating the assistant API into the existing workflow without changing a thousand of code lines.
The text was updated successfully, but these errors were encountered: