Environment
- Surface: Web
- Browser or app version: google chrome
- Model: GPT-5.6 Sol
Bug
What happened, and what did you expect?
An automatically generated conversation title was contaminated with an unrelated Chinese gambling brand string.
The title reads:
Analyze STNG 彩神争霸怎么样
The legitimate generated portion is “Analyze STNG.” The appended portion, 彩神争霸怎么样, has no semantic relationship to the conversation, which is entirely in English and concerns equity analysis of a US-listed shipping company. 彩神争霸 is a Chinese lottery and gambling brand string; 怎么样 translates roughly as “how about it.”
No Chinese text appears in my prompt, in the uploaded images, or in the model’s response body. The contamination is confined to the auto-generated title. The words “Analyze STNG” were also model-generated rather than typed by me, so the entire title string originates from the title-generation step.
Expected: an English title summarizing an English conversation.
Reproduction
Not reproducible on demand. The title was generated once at conversation creation and persists in the stored record. This is not a repeatable UI fault.
Minimal example of what produced it: a new conversation opened on Windows 11 in Chrome, with three chart images attached and the prompt “take a look at STNG and let me know your thoughts.” The model responded normally in English and the corrupted title was generated automatically.
Cross-device verification: the identical corrupted string renders in both ChatGPT for iOS and Windows 11 Chrome. Two operating systems, two clients, identical characters. This confirms the corruption is persisted server-side in the conversation record and is not a client-side rendering fault, browser extension, or input-method artifact.
Diagnostics
Exact string: Analyze STNG 彩神争霸怎么样
Screenshots attached: ChatGPT for iOS sidebar, and Windows 11 Chrome sidebar, both showing the same title.
Environment: ChatGPT Plus. Conversation originated on Windows 11 desktop in Chrome. Verified on ChatGPT for iOS. Home network.
Related public reports in the same cluster:
The reasoning-summary report indicates the affected surface may extend beyond title generation.
When it happened (with timezone) and how often:
September 10, 2026, approximately 1:33 PM MDT (UTC-6). Observed once. First occurrence I have noticed on this account.
