Using /feedback messes up with the user experience

Open 💬 1 comment Opened Mar 10, 2026 by bLightZP

What version of the Codex App are you using (From “About Codex” dialog)?

26.306.11636

What subscription do you have?

Plus

What platform is your computer?

Windows 10, fully patched

What issue are you seeing?

On Windows, I used the "/feedback" command to give some feedback.

It was taking a while, so I clicked the main window behind it to get back to writing a prompt and then I'm not sure if I either tried sending the prompt or if it froze even before I completed writing it, but essentially the text entry box became unresponsive (other controls worked fine).

I believe that the feedback confirmation window somehow moved behind the main window.

I was able to work myself out of the issue by switching to another conversation which popped the feedback Window, allowing me to close it and the chat box became responsive again.

What steps can reproduce the bug?

  1. Send feedback using "/feedback".
  2. Press the main codex window before the feedback confirmation window appears.
  3. Chat box becomes unresponsive.

What is the expected behavior?

Don't let the feedback window hide behind the main codex window.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗