[Windows][Desktop] Attachment removal and message actions are hidden until hover
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)?
26.908.9136.0
What subscription do you have?
ChatGPT subscription (exact tier is not shown in the Codex App)
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
In the Windows Codex desktop UI, important controls are visually hidden until hover or keyboard focus:
- The remove control for an image pasted into the unsent composer.
- Message controls such as Copy, rating, and timestamp.
This makes accidental image pastes difficult to undo and basic actions undiscoverable. For attachments, this is a send-safety issue: a user can accidentally send the wrong image before discovering the hidden hover target. No error message is shown.
What steps can reproduce the bug?
- Open any local Codex task in the Windows desktop app.
- Paste an image into the message composer.
- Move the pointer away from the attachment thumbnail.
- Observe that no remove control is visible.
- Hover the thumbnail or focus it with the keyboard; the remove control appears.
- View an existing message without hovering; Copy, rating, and timestamp controls are also hidden. Hover the message and they appear.
This reproduces consistently in dark theme and is independent of a specific task/session.
What is the expected behavior?
The remove button for every unsent attachment should remain visible at all times. Please also add an accessibility/display setting such as “Always show message actions”. Hover may reveal secondary controls, but a control that prevents accidentally sending the wrong attachment should not depend on hover.
Additional information
No private screenshots, chat content, task names, or local paths are attached. I searched existing openai/codex issues for an exact duplicate using attachment/remove/hover terms and did not find one.
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
No source file, test, or entry point is named in the report. Reproduce the issue in the Windows desktop composer and an existing message, then trace the attachment and message-action UI; done means the unsent attachment removal control is persistently discoverable and the requested message-action visibility behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- accessibility, design, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100