🦋 New version release#214
Merged
Merged
Conversation
brentrager
force-pushed
the
changeset-release/main
branch
from
ba220cf to
7142b2e
Compare
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@smooai/smooth-operator@1.22.7
Patch Changes
487d10b: Rust server: conversation auto-title (small model) +
rename_conversation(pearl th-d5b446).Session <uuid>name, a best-effort, detached, non-blocking task asks the fast/cheapgroq-gpt-oss-20bmodel for a short 3-6 word title over the first exchange and stores it as the conversationname. Fail-safe: any error (no gateway key, gateway failure, empty output, storage error) simply leaves the default name — a turn is never slowed or broken. The default-name guard (re-checked right before the write) means a manual rename is never clobbered, and a titled conversation won't re-fire.rename_conversation— new WS action{action, requestId, conversationId, title}: sanitizes/trims the title (rejects empty), 404s an unknown conversation, persistsnamevia the storage adapter's existingupdate_conversation, and repliesimmediate_response(200) with{ conversationId, title }.list_conversationsnow surfaces a meaningful conversationname(auto-title or manual rename — anything not the defaultSession <uuid>) as the sidebar title, falling back to the first-inbound message preview for un-titled conversations. Back-compat: every pre-titling conversation carried the default name, so the message-preview behavior is unchanged for them.Additive + back-compat. New tests cover title sanitization (quotes/markdown/whitespace/length), the default-name-only auto-title guard (mock gateway, never clobbers a manual name, no-key fail-safe), rename success + list surfacing, empty-title rejection, and unknown-id 404.