fix: agent loop to support non-OpenAI providers by selecting correct response handler #722
+2
−2
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.
This PR fixes an issue where the agent loop would hang or fail when using non-OpenAI providers (e.g., Gemini), due to hardcoded assumptions about the /responses endpoint.
🔧 Changes Made:
Adjusted agent loop logic to dynamically select the correct response handler based on both the provider argument and project config.
Prevents attempts to call unsupported OpenAI-specific endpoints when using alternatives.
Ensures a smooth response flow across providers with varying endpoint structures.
🐛 Fixes:
Resolves #706
✅ Expected Behavior:
The agent responds correctly regardless of whether OpenAI or another provider (e.g., Gemini) is used.
No hangs, timeouts, or silent failures on unsupported endpoints.