Skip to content

Fix forked thread name inheritance#26075

Merged
etraut-openai merged 1 commit into
mainfrom
etraut/fix-fork-thread-name
Jun 3, 2026
Merged

Fix forked thread name inheritance#26075
etraut-openai merged 1 commit into
mainfrom
etraut/fix-fork-thread-name

Conversation

@etraut-openai

Copy link
Copy Markdown
Collaborator

Fixes #25950.

Why

Forking a renamed thread could fall back to the source thread's first-prompt title because the fork path did not preserve the source's explicit name. That meant fork-of-renamed-fork flows could show stale sidebar labels even though the user had renamed the parent.

What changed

thread/fork now reads the source thread's distinct name, normalizes it, persists it onto materialized forks, and applies it to the returned API thread. Because the source name already excludes first-prompt pseudo-titles, forks inherit only an explicit user rename instead of stale generated metadata.

@fcoury-oai fcoury-oai left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Smoke tested and code looks good, approved.

@etraut-openai etraut-openai merged commit d8121f9 into main Jun 3, 2026
31 checks passed
@etraut-openai etraut-openai deleted the etraut/fix-fork-thread-name branch June 3, 2026 19:56
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 3, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Forking a renamed thread can reuse the stale first-prompt title

2 participants