Codex chat input layout, resizing, and attachment menu visibility issues
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
version 26.911.61220
What subscription do you have?
pro
What platform is your computer?
windows 11
What issue are you seeing?
The Codex chat UI has several layout and usability issues compared to the regular ChatGPT chat UI:
- The attachment menu opens downward and can disappear below the visible chat area.
In ChatGPT chat, after adding a file or writing a long message, the attachment menu can move downward and become partially or fully hidden. In Codex chat, the attachment menu behaves better because it stays visible above the input area. - The Codex chat input starts at the bottom of the page instead of being vertically centered like ChatGPT.
On the initial empty screen, ChatGPT starts from the center of the page, which feels correct. Codex starts from the bottom, leaving a large empty space above and making the experience feel broken. - The Codex chat input does not expand vertically enough for long messages.
When I write a long prompt, the input box stays very small. I cannot read the full message at once and I have to scroll line by line inside the tiny input box. This makes long prompts very hard to review before sending. - Codex chat does not have an expand or resize option.
ChatGPT has an expand button inside the chat input. Codex does not. Ideally, Codex should support resizing the input box, or at least provide an expand button so users can comfortably review long prompts.
Screenshot 1: ChatGPT attachment menu opens downward and can go below the visible area.
Screenshot 2: After adding a file, the attachment/menu area is pushed down.
shot 3: Codex attachment menu stays visible above the input area.
Screenshot 4: ChatGPT empty chat starts centered on the page. but Codex empty chat starts at the bottom and the input area stays too small.
What steps can reproduce the bug?
Open Codex chat.
Start a new chat.
Observe that the input box is positioned near the bottom of the screen instead of the center.
Type or paste a long prompt into the input box.
Notice that the input box does not grow vertically enough.
Try to review the full prompt before sending.
Notice that you must scroll inside a very small input area line by line.
Click the attachment/add button and compare the attachment menu behavior with the regular ChatGPT chat UI.
In ChatGPT chat, add a file or write a long message and observe that the attachment menu may open downward and disappear below the visible area.
In Codex chat, observe that the attachment menu stays above the input area, which is better behavior.
What is the expected behavior?
Codex chat should behave more like the regular ChatGPT chat UI:
- On a new empty chat screen, the input box should start around the vertical center of the page, not at the very bottom.
- The chat input should expand vertically when the user writes or pastes a long prompt.
- Users should be able to read and review long prompts comfortably before sending.
- Codex should provide an expand button or, preferably, a resize option for the input box.
- The attachment menu should always remain visible on screen and should not disappear below the chat input or outside the visible viewport.
- The attachment menu should intelligently open upward or downward depending on available screen space.
Additional information
No response
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.
Research direction
Open Codex chat on Windows 11 and reproduce the empty-screen, long-prompt, and attachment-menu behaviors described in the issue. Identify the chat input and attachment-menu entry points, then verify that the input is usable for long prompts, the empty state is positioned appropriately, and the menu remains visible within the viewport.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100