- Notifications
You must be signed in to change notification settings - Fork2k
Feat: separate tool_call_item and tool_call_output_item in stream events#974
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
legeRise commentedJun 30, 2025
hi i was just trying to get an effect of calling a tool with its name displays with a spinner and then after sometime the output so is it fixed Now? can i use it |
Yeah, just check out this PR and run the tests to verify. |
legeRise commentedJul 1, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
thank you so much. it works. hope it gets merged soon |
Suneel5 commentedJul 3, 2025
Waiting for it to get merged soon |
mattmorgis commentedJul 16, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@gdisk thank you for this PR 🙏 hoping they merge soon cc/@rm-openai in case you haven't seen yet. |
Summary
During my analysis of the streaming API (run_streamed) results, I noticed that tool_call_item and tool_call_output_item events are currently being emitted concurrently upon tool call completion (as evidenced in #831). This implementation conflates what should logically be distinct events. The current PR addresses this by properly separating these event triggers to better reflect the actual workflow.
Test plan
The test file is created in
tests
namedtest_stream_events.py
.Run the test script below to test.The test result is:
Issue number
#831
Checks
make lint
andmake format