Conversation titles sometimes end with stray punctuation/symbols in Codex App

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

Unknown; reproduced on current Codex desktop app builds on both Windows and macOS as of 2026-04-13

What subscription do you have?

Unknown

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64 (also reproduced on macOS)

What issue are you seeing?

Codex sometimes generates conversation titles with random trailing punctuation or symbols in the sidebar, such as }**, }}}, or ؟??}}; I have reproduced this on both Windows and macOS; in one recent repro the user message was normal Chinese text with only a single question mark, and in another repro the conversation included an attached screenshot whose OCR-like punctuation seemed to leak into the final title; the visible issue is that the final conversation title shown in the sidebar is not sanitized before display.

What steps can reproduce the bug?

1. Open the Codex desktop app; 2. Start a new conversation; 3. Send a short normal message; 4. This seems easier to trigger when the conversation contains Chinese text and or an attached screenshot, but I have also seen it when the typed text itself did not contain unusual symbols; 5. Return to the conversation list or sidebar; 6. Observe the auto-generated conversation title; actual result: the title sometimes ends with stray symbols such as }**, }}}, or ؟??}}; notes: reproduced on both Windows and macOS, and the strange suffix does not appear to come from intentional user input.

What is the expected behavior?

The auto-generated conversation title should be clean, human-readable, and stripped of stray punctuation or formatting artifacts; if OCR text from attachments is considered during title generation, it should still be normalized before the final title is displayed.

Additional information

Examples I have seen in the sidebar include titles ending with }**, }}}, and ؟??}}; this does not appear to be specific to one OS because I have seen it on both Windows and macOS; I am filing from Windows, but the same symptom has shown up for me on macOS as well.