π¦ New version release#237
Merged
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.
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.23.0
Minor Changes
d3d3abe: Two additive SEP-protocol enhancements on the streaming path (directive nav + business-card images), both optional and back-compatible.
Directive-over-SEP.
eventual_responsegains an optionaldirectivefield β an opaque client-side directive (e.g. a Navigate / ApplyView instruction) a host tool emitted this turn. The runner threads adirective_sinkinto theToolProviderContext(newwith_directive_sinkbuilder), drains it after the turn (last-write-wins, mirroring the citation sink), and carries the value ontoTurnResult::directive. The protocol layer never interprets the shape β the host client owns it, exactly likeresponse. Absent when no host tool wrote one, so the event is byte-for-byte unchanged for existing clients. Added tospec/events/eventual-response.schema.jsonandspec/actions/send-message.schema.json$defs/Response, and to the TypeScript SDK.Image-through-SEP.
send_messagegains an optionalimagesarray ({ url, detail? }) for multimodal turns. A new facadeUserImagetype flows from the inbound request intoTurnRequest::imagesand theToolProviderContext(newwith_imagesbuilder); when non-empty the runner maps each onto a coreImageContentand attaches them to the engine's user message viaAgentConfig::with_user_images(requires core0.16.2). Parsing is fail-soft (a malformedimagesentry is dropped, never rejects the turn). Empty/absent β a text-only turn, unchanged. Added tospec/actions/send-message.schema.json$defs/Requestand the TypeScript SDK.@smooai/smooth-operator-web-chat-example@0.0.11
Patch Changes