Repository navigation
Conversation
Use owned event timestamps and observed size changes alongside filesystem mtime. Bootstrap complete tail records, including oversized records, without recounting tokens. Preserve definite requests and real inactivity warnings.
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.
Windows can retain a rollout's old modification time while Codex keeps the writer open. This can produce a blinking CHECK SESSION warning after three minutes even while new events are being written, and can hide fresh activity when the filesystem timestamp falls outside the active horizon.
Track activity using observed file-size changes and owned event timestamps alongside modification time. At startup, inspect the recent JSONL tail and extend through its overlapping record so large tool results and reasoning records still establish activity. Unchanged polls and repeated reads of an incomplete record do not refresh activity; genuine quiet periods, approval requests, and input requests retain their existing behavior. Token accounting is unchanged.
Regression coverage includes stale timestamps at startup and after appends, unchanged polls, partial records, large records and exact tail boundaries, inherited history, future timestamps, and approval/input precedence. The README describes the Windows behavior.
Validation on Windows:
Local race instrumentation was unavailable because this Windows environment has no configured C compiler (CGO_ENABLED=0). The repository's existing CI runs race tests on Windows, Linux, and macOS.