Repository navigation
fix(chatgpt): retry transient WebSocket response failures - #268
Merged
Merged
Conversation
danielkov
enabled auto-merge (squash)
October 12, 2026 16:02
![kit-code-agent[bot]](https://avatars.githubusercontent.com/in/4797102?s=60&v=4){kind=small}
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
1 participant
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.
Summary
Pin
agentkit-provider-openaito 0.10.13 so ChatGPT sessions retry correlated transient WebSocket response failures. Add a loopback regression that keeps the failed socket open and requires a full-request retry on a fresh socket.Motivation
An accepted response that fails with
server_errorand status 503 currently terminates the session after one attempt, before the configured retry policy can run. This adopts the published fix from AgentKit #33.Technical details
The lockfile changes only the provider version and checksum; dependencies and enabled features are unchanged. The published archive matches the merged upstream commit.
Recovery retains the upstream
store:false, response-ID correlation, and output-supersession safeguards. Malformed sequence numbers are now rejected as protocol errors rather than silently ignored.