fix(status): keep Codex long turns visible beyond the rollout tail - #249
Merged
Merged
Conversation
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.
fixes Codex threads losing their working status once output pushes
task_startedbeyond the 256 KiB rollout tail. the shared reader now retains an append cursor and the latest turn marker, with a bounded cache, partial-record retries, truncation reset and the existing stale-turn timeout.regression failed with
Noneinstead ofbusybefore the change. 981 Rust tests and 1397 frontend tests pass, along with check, Clippy and the bundle budget. an isolated window reading an active Codex rollout displayedrunning; the first query took 45 ms and subsequent queries about 3 ms. remote clients were not exercised.