openai / openai/codex

Bug: Message composer/text area disappears after ChatGPT finishes responding.

Open
#43,091 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug
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.901.41600

What subscription do you have?

Chatgpt Plus

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

Bug: Message composer/text area disappears after ChatGPT finishes responding.

Platform: ChatGPT desktop app for macOS

Workaround:
Switching to another conversation and then returning to the original conversation makes the text area appear again.

Additional information:
I originally experienced this on my existing Mac installation. I have now reproduced the exact same issue on a freshly formatted iMac with a clean macOS setup, so it does not appear to be caused by local settings or an old installation.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a07329-0070-7872-bcf9-15f0db1b2264

What is the expected behavior?

It should not disappear

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the disappearing composer in the macOS desktop app after a response finishes, using feedback ID no-active-thread-01a07329-0070-7872-bcf9-15f0db1b2264. Trace the conversation UI behavior around switching away and back; done means the message composer remains visible without changing conversations.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.