feat: implement Responses API #437
Open
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
|
Hope it will be merged soon! |
|
Thank you for contribution 🙌 ! let's merge your progress for now, and add streaming in a separate PR. |
aallam
approved these changes
Apr 23, 2025
aallam
requested changes
Apr 23, 2025
…Responses-API # Conflicts: # openai-client/src/commonMain/kotlin/com.aallam.openai.client/OpenAI.kt
|
Is there something I need to do to fix the workflow? |
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.
Describe your change
This PR implements the new Responses API.
Note: I've only tested my use cases happy paths so far. Streaming support is still missing, so this isn’t the final state. Depending on feedback, this might go through another iteration or two, or it may be merged with the remaining bits addressed later. Just wanted to get this out there to share progress :)
What problem is this fixing?
The library currently lacks support for the Responses API, which means features like built-in tools weren't usable. This change adds initial support and sets the groundwork for full integration.