fix(openai): support websocket custom base URLs#29636
Conversation
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
The following comment was made by an LLM, it may be inaccurate: Potential Duplicate FoundPR #29394: feat(opencode): add experimental OpenAI Responses WebSocket Why it's related:PR #29394 adds the experimental OpenAI Responses WebSocket feature, while PR #29636 (current) fixes support for custom OpenAI base URLs with that WebSocket implementation. These PRs are closely related—the current fix likely addresses an issue discovered in PR #29394's feature. You may want to check if #29394 is already merged and whether this fix should be incorporated there or if they should be reviewed together. |
Issue for this PR
Type of change
What does this PR do?
Allows codex oauth websocket to handle custom openai baseURL that use
/responsespathHow did you verify your code works?
added logs to see I was connected through websockets for both default openai and through a custom baseURL, see below
Screenshots / recordings
Checklist