UX for Chat in the ChatGPT Mac App
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
v26.908 (Latest, just updated)
What subscription do you have?
Plus $20/month
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
-
When I submit a prompt, the response streaming is not smooth and the response leaves a large whitespace on my screen (basically the last line of the response is near the top of my screen instead of being at the bottom near the text box).
As soon as I submit the next prompt, the whole screen jumps which is displeasing, to remove the whitespace for the next response stream. And then the same thing described above happens.
The wesbsite does not have this just the app. -
Also there are random UI in the response which don't have any connection to the response.
- The reference modals are distracting, as every time the response is referencing a document, it creates a distracting box that breaks the flow of the response and makes it harder to read
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a0bbc0-ec92-7dd1-bdb5-0fb1b8bfd975
What is the expected behavior?
No response
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
No source files or tests are named. Start by reproducing the three reported behaviors in the Mac app using feedback ID no-active-thread-01a0bbc0-ec92-7dd1-bdb5-0fb1b8bfd975; done means smooth streaming without large whitespace or jumps, no unrelated response UI, and less disruptive reference modals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100