Distinguish unknown Codex thread statuses - #276
Draft
myobie wants to merge 1 commit into
Draft
Conversation
myobie
force-pushed
the
agent/issue-264-unknown-status
branch
from
August 18, 2026 07:28
86cb211 to
706390a
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
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
CodexHoldReason::UnknownStatus.turn/completed.Why
The trailing
observe_thread_statusarm mapped every future status word toSystemError. That mapping reported a system error that Codex did not send.Impact
Operators can distinguish a real
systemErrorfrom an unrecognized provider status. The unknown status remains a safe delivery hold.Validation
cargo test -p st2 --lib codex_app_server::tests -- --nocapture: 39 passed.git diff --check: passed.cargo fmt --all -- --check: blocked by existing repository-wide formatting drift outside this change.Addresses the unknown-status defect described in #264.