fix: preserve ChatGPT OAuth refresh token#25765
Open
kill74 wants to merge 1 commit intoanomalyco:devfrom
Open
Conversation
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.
Issue for this PR
Closes #25757
Type of change
What does this PR do?
Preserves the existing ChatGPT OAuth refresh token when refreshing the access token.
The old refresh path always saved
tokens.refresh_token. If the refresh response did not include a new refresh token, the stored auth could become invalid after restart. This keeps the previous refresh token unless the server returns a replacement.It also checks that initial browser/headless login responses include a refresh token before saving OAuth auth.
How did you verify your code works?
Ran
bun run --cwd packages/opencode typecheck.Screenshots / recordings
N/A
Checklist