You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Long-running threads can outgrow their initial title. Would opt-in automatic title updates be useful when the thread’s objective materially changes?
I’m testing this in a fork, built on the unmerged #10720. The link is to a source branch; there isn’t a packaged test release.
The agent working in the thread can update its generated title using the context it already has. No separate title-generation call is needed. Manually chosen titles stay protected, initial naming remains unchanged, and age, activity and cooldown requirements limit churn. Snoozed, archived and settled threads are excluded.
This came up in #7333, whose author primarily wants explicit renaming from a skill. Automatic updates are a separate, optional policy. An upstream contribution would aim to build on the rename/regenerate tooling in #2829.
The fork includes history and undo, which could remain a separate contribution. QA is ongoing and testers are welcome. Is this behavior something maintainers would want to explore?
Implemented with GPT-6 Astra in Codex. Reviewed with Claude Fable 5.1 and independently with GPT-6 Astra.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Long-running threads can outgrow their initial title. Would opt-in automatic title updates be useful when the thread’s objective materially changes?
I’m testing this in a fork, built on the unmerged #10720. The link is to a source branch; there isn’t a packaged test release.
The agent working in the thread can update its generated title using the context it already has. No separate title-generation call is needed. Manually chosen titles stay protected, initial naming remains unchanged, and age, activity and cooldown requirements limit churn. Snoozed, archived and settled threads are excluded.
This came up in #7333, whose author primarily wants explicit renaming from a skill. Automatic updates are a separate, optional policy. An upstream contribution would aim to build on the rename/regenerate tooling in #2829.
The fork includes history and undo, which could remain a separate contribution. QA is ongoing and testers are welcome. Is this behavior something maintainers would want to explore?
Implemented with GPT-6 Astra in Codex. Reviewed with Claude Fable 5.1 and independently with GPT-6 Astra.
All reactions