Skip to content

Return None when auth refresh fails#20092

Merged
gpeal merged 2 commits intomainfrom
gpeal/return-none-on-refresh-failure
Apr 28, 2026
Merged

Return None when auth refresh fails#20092
gpeal merged 2 commits intomainfrom
gpeal/return-none-on-refresh-failure

Conversation

@gpeal
Copy link
Copy Markdown
Collaborator

@gpeal gpeal commented Apr 28, 2026

Right now, if Codex winds up in a state with auth but it can't refresh the token, the user is left with an unhelpful message that says to log out and log back in again.

Ultimately, we should prevent that from happening but if it does, returning None will allow the caller to redirect the user back to the login page

@gpeal gpeal marked this pull request as ready for review April 28, 2026 22:53
Copy link
Copy Markdown
Collaborator

@celia-oai celia-oai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. will investigate how we got into this inconsistent state in the first place

@gpeal gpeal merged commit 5e6cbba into main Apr 28, 2026
25 checks passed
@gpeal gpeal deleted the gpeal/return-none-on-refresh-failure branch April 28, 2026 23:15
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants