Repository navigation
Backport 2369 to 0.10.x release branch - #2375
Merged
EItanya merged 1 commit intoJul 31, 2026
Merged
Conversation
Users can now use the Responses API either directly with OpenAI or via a
gateway like AgentGateway. Here's an example with agent gateway.
```yaml
apiVersion: kagent.dev/v1alpha2
kind: ModelConfig
metadata:
name: openai-responses
namespace: kagent
spec:
provider: OpenAI
model: gpt-5.4-mini
apiKeyPassthrough: true
openAI:
baseUrl: http://agentgateway-proxy.agentgateway-system.svc/openai
apiFormat: responses # NEW! <- If not provided, uses chat completions API
```
Note that certain features from Responses API like native tools and
stateful chaining are not supported for now since they're only available
when using with OpenAI's servers. For those interested, it can be a
follow up to add those features in kagent harness.
---------
Signed-off-by: Jet Chiang <[email protected]>
EItanya
approved these changes
Jul 31, 2026
onematchfox
added a commit
to onematchfox/kagent
that referenced
this pull request
Sep 3, 2026
Responses API is required in order to use reasoning effort with newer Open AI models. kagent-dev#2369 (backported to `v0.10.x` in kagent-dev#2375) introduced support for use of the Responses API (configured via ModelConfig). However, that PR was strictly limited to golang agents and at present Python agents completely ignore the configuration and as such requests to a new model configured with reasoning effort will fail. This PR completes kagent-dev#2369 by ensuring that Python ADK agents also make use of the Responses API as per model configuration. Signed-off-by: Brian Fox <[email protected]>
onematchfox
added a commit
to onematchfox/kagent
that referenced
this pull request
Sep 3, 2026
Responses API is required in order to use reasoning effort with newer Open AI models. kagent-dev#2369 (backported to `v0.10.x` in kagent-dev#2375) introduced support for use of the Responses API (configured via ModelConfig). However, that PR was strictly limited to golang agents and at present Python agents completely ignore the configuration and as such requests to a new model configured with reasoning effort will fail. This PR completes kagent-dev#2369 by ensuring that Python ADK agents also make use of the Responses API as per model configuration. Signed-off-by: Brian Fox <[email protected]>
onematchfox
added a commit
to onematchfox/kagent
that referenced
this pull request
Sep 4, 2026
Responses API is required in order to use reasoning effort with newer Open AI models. kagent-dev#2369 (backported to `v0.10.x` in kagent-dev#2375) introduced support for use of the Responses API (configured via ModelConfig). However, that PR was strictly limited to golang agents and at present Python agents completely ignore the configuration and as such requests to a new model configured with reasoning effort will fail. This PR completes kagent-dev#2369 by ensuring that Python ADK agents also make use of the Responses API as per model configuration. Signed-off-by: Brian Fox <[email protected]>
onematchfox
added a commit
to onematchfox/kagent
that referenced
this pull request
Sep 4, 2026
Responses API is required in order to use reasoning effort with newer Open AI models. kagent-dev#2369 (backported to `v0.10.x` in kagent-dev#2375) introduced support for use of the Responses API (configured via ModelConfig). However, that PR was strictly limited to golang agents and at present Python agents completely ignore the configuration and as such requests to a new model configured with reasoning effort will fail. This PR completes kagent-dev#2369 by ensuring that Python ADK agents also make use of the Responses API as per model configuration. Signed-off-by: Brian Fox <[email protected]>
EItanya
added a commit
that referenced
this pull request
Sep 4, 2026
Responses API is required in order to use reasoning effort with newer Open AI models. #2369 (backported to `v0.10.x` in #2375) introduced support for use of the Responses API (configured via ModelConfig). However, that PR was strictly limited to golang agents and at present Python agents completely ignore the configuration and as such requests to a new model configured with reasoning effort will fail. This PR completes #2369 by ensuring that Python ADK agents also make use of the Responses API as per model configuration. Signed-off-by: Brian Fox <[email protected]> Co-authored-by: Eitan Yarmush <[email protected]>
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
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.
#2369