Repository navigation
Recover OpenAI subscription authentication from Telegram - #22
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Expired or revoked OpenAI subscription credentials now produce actionable Telegram messages. The owner can run
/login openaiin a private chat, approve a device code in their browser, and resume using Lethe without CLI access or a restart./login canceland cached authentication status remain available without a working model.The OAuth client serializes refreshes within the process, retries an unauthorized request once, atomically persists rotated credentials, and retains them after a temporary save failure. Background notices are throttled after successful delivery and release the interactive gate before backoff. Sign-in codes are omitted from reaction metadata, and cancellation distinguishes pending approval from credentials already saved.
Validation: 553 local Rust tests passed; release build,
cargo fmt --check, andgit diff --checkpassed. Loopback regressions cover refresh concurrency, credential rotation and persistence failures, bounded retries, device login, cancellation, and sign-in code redaction. Security and functional reviews reported no remaining concrete findings on the final source. Live OpenAI approval and Telegram recovery will require the owner's sign-in after deployment.Operational assumptions: one Lethe process per token file, writable persistent credentials, and no nonempty
OPENAI_AUTH_TOKENoverride for browser renewal. Existing CI and release provenance gates remain unchanged.