Repository navigation
feat(codex): report live unsaved threads without queueing - #194
Merged
Merged
Conversation
abruption
force-pushed
the
fix/166-unsaved-codex-diagnostic
branch
from
September 24, 2026 12:14
6000cc0 to
ed1034b
Compare
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
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.
Fixes #166.
When no saved Codex thread exists, resolution now checks the UUID-specific writer lock in known homes. Exactly one stable live writer produces a distinct thread_not_yet_persisted refusal with first-turn guidance; no queueing is attempted. A missing or stale lock retains thread_not_saved_in_known_homes, and saved-thread/home selection is unchanged. Doctor performs a bounded read-only scan of the selected home and reports the count of live unsaved writers without exposing thread IDs.
Validation: 515 tests passed locally (11 skipped); generated standalone and git diff --check passed. Existing sqlite ResourceWarnings in unrelated backup snapshot tests remain.