OpenAI Codex
From a confusing copy shortcut to a reproducible exit bug: testing what the terminal actually does, then sharing the evidence upstream.
- Contribution
- Manual reproduction, environment comparison and a published follow-up in issue #48527. No code patch or merged fix claimed.
- Environment
- Linux Mint 22.1 / Cinnamon X11; Codex 0.157.1; GNOME Terminal 3.52.0 and Ghostty 1.3.1.
- Method
- I carried out the desktop selection, paste and exit tests. Codex agents assisted with versioned source research, test guidance and evidence capture.
- Date
- 27 September 2026. Findings describe the tested version and setup.
What changed our understanding
The report
A Codex user could no longer select the conversation name and ID in the footer. They also reported trouble copying question options and a missing conversation name on exit. They needed those details to resume the right conversation later.
My first question helped establish that Shift-drag still worked. I then tested the behavior in two terminals rather than assuming the report was specific to Ghostty.
Selection is not the clipboard
Ordinary dragging could select response text but not the footer name. In a live async question, ordinary dragging also failed to select option text. Native Shift-drag copying worked, including pasting the option into a text editor and the question’s Other field.
Two highlights could remain visible at once. Ctrl+Shift+C copied the terminal’s selection; Ctrl+C, while Codex’s copy hint was visible, copied Codex’s selection. Both produced the expected text. That separated a selection-coverage gap from a general clipboard failure.
I also verified that Copy & Follow copied the text and returned to the latest output. Running /status, then immediately /copy, exposed working dedicated actions for the conversation name and ID.
The important second test
The first named-session exit printed both the name and ID. That was an embedded session, so it did not settle the original report.
A second disposable session connected explicitly to the existing local daemon over a Unix socket. The live connection and saved name were checked before quitting. Its exit output included the correct ID and reconnect command, but omitted the name. The embedded session served as the control.
The versioned source explains the difference: the disconnect branch returns before the embedded name guidance. This reproduces the symptom under known conditions; it does not establish which connection mode the reporter used.
Contribution & limits
I posted the terminal comparison, live-question findings, copy workarounds and daemon-versus-embedded exit result in the existing issue, then asked the reporter about their daemon setup.
This is a contribution through investigation and bug reporting. I did not submit or ship a Codex fix. The reporter used a different Ghostty build, their exact question UI is unknown, and the tests do not establish behavior in every terminal or later release.