fix(codex): preserve native item start times - #13525
Conversation
- Use Codex item start timestamps for turn items and execution nodes - Assign first-seen times to items without a native start event
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — The PR narrowly corrects Codex timeline timestamps by preserving native item start times, with a focused replay test covering command and compaction items. It does not alter provider execution, schemas, defaults, or deployment behavior. You can add or adjust custom eligibility rules. Learn more. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
What Changed
Codex turn items now keep their own native start times instead of inheriting the turn start time. Subagent activity is grouped even when there is only one subagent, and collapsible panels animate consistently.
Why
Items within a Codex turn can start at different times. Using the turn start time made their timestamps inaccurate. Grouping single subagents also gives their expanded details the same disclosure behavior as larger groups.
UI Changes
No screenshots are needed. The change updates subagent grouping and disclosure behavior without changing the visible design.
Checklist