VS Code Codex chat shows misleading visible message order and timestamps
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reproducing the ordering and timestamp behavior in the Codex chat UI inside VS Code on Windows, using the message examples and checking scroll position or lazy loading. Inspect message ordering, timestamp rendering, and grouping; done means each user message appears before its matching assistant reply and the visible timestamps are easy to follow.
Written by the indexing model from the issue text.
Description
Problem
In Codex inside VS Code on Windows, the chat panel can show a visually confusing message order and timestamps.
In the same visible chat area, an older assistant reply appears above while a different user question appears below, making it look like the assistant replied before the question was asked.
What I observed
- An assistant message ending with:
make a one-click PC slowdown check scripthelp update Codex step by step first
- was shown above
- with timestamp:
Thursday 3:42 PM
At the same time, lower in the same visible chat area:
- a user message:
What is the issue in chat? - was shown below
- with timestamp:
Thursday 3:37 PM
Also, the actual reply to What is the issue in chat? appeared as a different assistant message starting with:
The issue in this chat is simple:Your same message was sent multiple times.
This makes the visible order look wrong even though the underlying thread may still be intact.
Expected behavior
- Each user message should clearly appear before its matching assistant reply.
- Visible ordering in the chat panel should not make older assistant replies appear as if they belong to newer user questions.
- Timestamps and message grouping should be easy to follow.
Actual behavior
- Messages from different turns appear visually mixed in the visible panel area.
- This creates confusion about which reply belongs to which question.
- It can look like the assistant replied before the user asked.
Environment
- Codex inside VS Code
- Windows
- India Standard Time (UTC+05:30)
Notes
Possible areas to check:
- message ordering in the Codex chat UI
- timestamp rendering/grouping
- scroll position or lazy loading causing mixed visual sequencing
- whether messages from different turns are shown in a misleading visible order
I have screenshots available if needed.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·