[codex] Handle missing CLI auth code tokens#710
Merged
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
2 participants
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
Missing opaque CLI login tokens now stop before signed auth-code validation and render a stale-link response instead of the generic invalid-auth-code path.
Why
Freebuff occasionally logs
Invalid Freebuff CLI auth codefor 43-character opaque login tokens whose token lookup returnsmissing. Those tokens are not signed auth-code payloads, so parsing them as signed codes produces empty fields and a misleading warning/user message.Changes
missingauth-code resolution branch in Freebuff onboarding.infofor correlation without treating them as invalid signed codes.Validation
bun --cwd freebuff/web typecheckbun --cwd web typecheckbunx prettier --write freebuff/web/src/app/onboard/page.tsx web/src/app/onboard/page.tsxgit diff --check