Files
pipelines/docs/notes/codex-message-timestamps.md
T

6 lines
1.1 KiB
Markdown

# Codex transcript timestamps
Codex thread history previously flattened items without setting `ChatMessage.CreatedAt`, so clients correctly omitted timestamps. The installed App Server schema records `Turn.startedAt` in epoch seconds; individual historical ThreadItems have no creation timestamp. Forward the recorded turn start, converted to milliseconds, to both user and assistant rows (including failed-turn detail). This is turn-level timing, not an exact per-item send time. Missing, negative and out-of-range values remain absent; never substitute server read/render time. Pagination/order and client message identities are unchanged.
Verified against the installed Codex generated schema (`v2/ThreadTurnsListResponse.json`, `ServerNotification.json`). Tests exercise real JSON history decoding, pagination order, user/assistant identity, repeated reads, in-progress turns, legacy missing times and invalid/overflowing values. Focused Codex tests passed. Deployment must wait for all shared runs and chat turns to settle; the first Codex bridge upgrade cannot retroactively preserve outstanding connection-bound approvals/questions.