JustPaste.it

ChatGPT conversation titles changed after scheduling

ChatGPT conversation titles changed after scheduling

Conversation-title-change bug
11 October 2026 | Version 1.2

Creating a scheduled task was followed by an existing ChatGPT conversation displaying the task’s name in place of its manually assigned title. Two earlier October observations and a subsequent controlled two-task experiment are documented below. The technical cause remains unconfirmed.

“ChatGPT cannot reliably make the organisational changes I ask it to make, but it can apparently make organisational changes I specifically did not ask for.”

What happened

On 10 October 2026, using ChatGPT web in Chrome on Windows, a conversation manually named “000B-ADMIN-EM” appeared in the sidebar as “Dots UK availability” -- the name of a recurring task created inside it.

Opening that entry showed the existing conversation and its scheduled-task card. The reporting user checked that the original conversation URL remained unchanged. No rename had been requested, and the title was restored manually.

Later that day, the same apparent behaviour occurred in the conversation documenting this bug. That conversation had been manually named “CM-03-Conversation-Title-Changes”. After a recurring task was created inside it, the displayed title became “CM-03 Support Reply Watch”, matching the task name.

The original title initially remained visible after scheduling. By approximately 20:35–20:36 BST (UTC+1), the changed title appeared in the sidebar. At approximately 20:40 BST, ChatGPT Search, including its Chats filter, also displayed the unwanted title. This second changed title was left in place for investigation.

Controlled experiment -- 11 October 2026

In the user-reported controlled experiment, one existing test conversation was initially named CM-03-Test-Original. The user did not manually rename it during the experiment.

  1. Task A was created inside that conversation with a harmless reminder scheduled seven days later. After creation, the displayed conversation title appeared as CM-03-Test-Alpha.

  2. Task B was then created inside the same conversation. Its exact task name was CM-03-Test-Original; it too was a harmless one-time reminder scheduled seven days later. The conversation title then appeared again as CM-03-Test-Original.

  3. Neither task had executed during the observation window. The changes followed task creation, not reminder execution.

The observed title sequence was CM-03-Test-Original -- CM-03-Test-Alpha -- CM-03-Test-Original. Exact creation, execution and title-rendering times are omitted because they have not been independently verified for this update.

This supports an association between task creation and the displayed conversation title. It does not establish the backend component, whether an automatic naming heuristic or synchronization effect is responsible, whether all accounts are affected, or whether extensions play any role.

Why it matters

Manually assigned conversation titles help users identify ongoing work, find discussions and maintain continuity across Projects and handovers. An unexpected replacement creates uncertainty about which conversation an entry represents and requires additional checking and restoration.

The reported experience exposes an ironic contrast: expressly requested help with creating, naming, placing or reorganising conversations was unavailable directly in the reporting user’s workflow, while creating a scheduled task apparently triggered an unrequested change to a deliberately assigned title.

As the reporting user put it in the Support report: “ChatGPT cannot reliably make the organisational changes I ask it to make, but it can apparently make organisational changes I specifically did not ask for.”

The practical concern is straightforward: a title deliberately chosen by the user should remain stable unless the user authorises its replacement.

What the evidence establishes

The October observations show task names appearing as existing conversation titles without a requested rename. The second occurrence affected both the sidebar and Search results.

They do not establish whether the underlying conversation metadata changed or whether those interfaces shared an incorrect title association. Scheduling is associated with the observed changes; the exact cause remains unconfirmed.

An analogous August incident is recorded in preserved conversation history, without fresh browser-metadata verification. A subsequent controlled two-task experiment is documented above.

Support status and requested outcome

OpenAI Support case #16944707 contains both October occurrences. At the Support-thread check on 11 October 2026, the latest reply was dated 10 October at 20:49 BST. It acknowledged the second occurrence and the changed title appearing in both the sidebar and Search.

Support’s AI-assisted agent requested the Chrome version, enabled extensions and, if feasible, an Incognito comparison. At that check, no technical diagnosis, confirmed engineering escalation or correction had been received.

The requested outcome is to investigate the behaviour and preserve manually assigned conversation titles when scheduled tasks are created or modified.

Community discussion

The existing Forum contribution has been updated with the two-task experiment:

https://community.openai.com/t/bug-manually-assigned-chat-names-can-be-overwritten-automatically/1400079/2

Related public reports and discussions

The following sources describe matching or related user experiences.
They do not establish a shared technical cause.

Source check: The earlier related-source checks used retrieved page text. The CM-03 page and existing Forum contribution were inspected in the browser for this update. The earlier case-status account is retained from the prior Support-thread check; no fresh Support check was made for this publication. The experiment is reported from the supplied handover and publication drafts. Private conversation URLs and unrelated Project content are excluded.


ChatGPT, AI and Technical Notes
Back to the Start page