Skip to content

Conversation

@notgitika
Copy link
Contributor

@notgitika notgitika commented Oct 3, 2025

Description

This PR implements OpenAI Responses API as a separate model provider supporting streaming, structured output and tool calling.

Note: this commit does not include the extra capabilities that the Responses API supports such as the built-in tools and the stateful conversation runs.

Related Issues

#253

Documentation PR

TODO; coming next: will be adding a section for the Responses API within the existing openai model page

Type of Change

New feature

Testing

Added a unit test file similar to the existing test_openai.py model provider. Reusing the integ tests in the same file test_model_openai.py using pytest.parameterize with OpenAIResponses model so that I could test that the funcitonality is the same between the two models.

I ran everything in the CONTRIBUTING.md file.

hatch run integ-test
================== 81 passed, 68 skipped, 49 warnings in 106.56s (0:01:46) ==========

hatch run test-integ tests_integ/models/test_model_openai.py -v

============= 18 passed, 2 skipped in 13.44s =============

pre-commit run --all-files

  • I ran hatch run prepare --> yes, all tests pass

Checklist

  • I have read the CONTRIBUTING document
  • I have added any necessary tests that prove my fix is effective or my feature works
  • I have updated the documentation accordingly
  • I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

"""
match event["chunk_type"]:
case "message_start":
return {"messageStart": {"role": "assistant"}}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reach out to @zastrowm , but I believe we can make this more readable by now returning the typed StreamEvents rather than the dictionaries

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was looking into this briefly but did not implement this. I will talk to him about this and maybe we can implement this in the next iteration.

@fsajjad
Copy link

fsajjad commented Oct 24, 2025

Hey Team, this is one of the feature my customer request and concerned as blocker from adopting Strands Agent. They mentioned Strands currently only support deprecated chatcompletion API and not responses API. When can we expect this to be merged? and will this also enable streaming structured output?

Copy link
Member

@dbschmigelski dbschmigelski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A major version bump is proposed in #1370.

Adding a comment here that we would need to consider when the user has v1 installed compared to v2.

For example

import pydantic
from packaging import version

# Detect the version once at the module level
PYDANTIC_V2 = version.parse(pydantic.VERSION) >= version.parse("2.0.0")

if PYDANTIC_V2:
    from pydantic import ConfigDict
    def get_model_fields(model):
        return model.model_fields
else:
    def get_model_fields(model):
        return model.__fields__

@notgitika notgitika force-pushed the gitikavj/add-openai-responses-model branch from 7c05e84 to 8eea5d9 Compare January 21, 2026 06:16
@codecov
Copy link

codecov bot commented Jan 21, 2026

Codecov Report

❌ Patch coverage is 91.41631% with 20 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/strands/models/openai_responses.py 91.41% 4 Missing and 16 partials ⚠️

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants