fix: monitor current Codex capacity events#15
Merged
Conversation
makerjackie
marked this pull request as ready for review
July 16, 2026 09:37
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.
What changed
~/.codex/logs_*.sqliteevent database for model-capacity failurescodex-tui.logreader as a compatibility fallbackRoot cause
Current Codex Desktop builds no longer append runtime events to
~/.codex/log/codex-tui.log. Auto Retry was running, but its only production detector was watching that stale file, so new capacity failures were invisible.Verification
./test.shtarget = 'codex_core::session::turn'and contain the exactTurn error: Selected model is at capacity...messagegit diff --check