Restore Optionality for Handling App Close behavior (clicking the X)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Windows Desktop App
What feature would you like to see?
As of today, 2026/09/15 I can no longer find the option regarding what to do when I click the X to close out of ChatGPT. I don't care what you want to set the default behavior to, minimize to tray or quit the application, but I do want the choice.
This came up for me today when I noticed I had closed ChatGPT and it remained open in the System Tray (as normal for me) but the process had 12 Codex subprocesses and was using a full 1GB of RAM AND slowly ramped up to 1.4GB. That feels a bit high, especially with little or no transparency as to what all of those codex processes were doing, why they were there, and why it takes 1.4GB or RAM to make it happen.
I'm requesting that you restore the option for the user to decide the behavior of how the application responds when the window is closed.
Thank you!
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
Start by locating the Windows Desktop App handling for window-close and system-tray behavior, then inspect how Codex subprocesses remain active after closing. Done means users can choose whether clicking X minimizes to the tray or quits the application, with both choices behaving consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100