Repository navigation
fix: Codex CLI keeps its sign-in when one of its processes renews with a copy another already used - #342
Merged
cyberpapiii merged 1 commit intoOct 7, 2026
Conversation
…h a copy another already used Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cyberpapiii
enabled auto-merge (squash)
October 7, 2026 02:26
cyberpapiii
deleted the
ship/codex-cli-keeps-its-sign-in-when-one-of-its-proc
branch
October 7, 2026 02:32
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.
Codex CLI runs as several processes that share one saved sign-in. Each keeps the refresh token it read at start, so one renews and another presents the spent copy later, often about an hour on. Plug took that for a replay after 60 seconds and revoked the whole sign-in, which signed every Codex process out.
A spent refresh token presented by the same client is now accepted for a week while the sign-in is still live. Past that, or from another client, it still revokes the family.
Also drops the client audit line from docs/STATUS.md: the owner confirms GrokBot is told apart correctly.
Tested: ./scripts/dev.sh, and installed with dev-install.sh.
🤖 Generated with Claude Code