Sync Threadleaf titles to Codex sessions - #17
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
thread/name/set.0.1.1.Why
Threadleaf conversations were persisted by Codex and appeared in Codex recent tasks, but their user-facing title could fall back to the raw first prompt, including injected page context. Threadleaf already derives a cleaner conversation title, so the provider session should receive the same title.
Impact
New and resumed Threadleaf conversations use the same readable title in Threadleaf and Codex recent tasks. Providers that do not support session titles are unchanged.
Validation
npm run typechecknpm test(43 passing)npm run buildReply with exactly SECOND_OK. This intentionally lo…matched the persisted Codex thread title for the same session ID.