Repository navigation
feat: titleFrame - send the generated title after stream.done (0.8.0) - #13
Merged
Merged
Conversation
…done A streamed message with titleFrame: true no longer waits for the title model before stream.done: the turn ends and the conversation is given back as soon as the answer is stored, and the title follows on the same stream as a stream.title frame. Without the flag nothing changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017S1VJk5SuTVqr4dr2at3cH
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017S1VJk5SuTVqr4dr2at3cH
4 tasks done
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.
Summary
A chat's copy, feedback and other answer buttons appear only on
stream.done. On a conversation's first message,finalizeTurnsent that frame only after the title model answered, so the answer sat finished on screen for a second or more (up to the title timeout) before its buttons showed.titleFrameon a streamed message. With"titleFrame": true:stream.donegoes out as soon as the answer is stored, without a title.conversation_busy, and therateLimitslot is released.stream.titleframe ({ conversationId, title }), followed by thesession.titleevent.stream.donewhen no title is made.stream.done, the JSON answer and the event order are as before.ActiveRun.handBack()/sendLate()/afterReleasekeep the starting connection open after the run is over.emitis closed by then, so nothing more goes into the run's log.StreamTitleEvent. Swagger and the streaming / chat-experience guides are updated.chat-ui (next PR) sends the flag when its callbacks take the title.
Test plan
npx vitest run: 1840 passed (memory, SQLite and Mongo providers; Postgres skipped locally).stream.donecomes without a title while the title model is still blocked.stream.titlecomes afterstream.done, and the title is stored once with onesession.titleevent.stream.done.npm run lint,npm run build🤖 Generated with Claude Code
https://claude.ai/code/session_017S1VJk5SuTVqr4dr2at3cH