🦋 New version release - #477
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.53.0
Minor Changes
0e8f36e: Add the
choicesRich Interaction kind (a structured multiple-choice ask, modeled on Claude Code's AskUserQuestion) as the second reference kind in the Rust implementation, plus its shared JSON-Schema contract the other servers + web SDK mirror.An agent raises
request_choiceswith 1–4 questions, each{ question, header (short ≤12-char label), options: [{ label, description }] (2–4), multiSelect? }and areason. On a channel that declared thechoice_chipscapability the turn parks and the client renders chips/menus (interaction_required { kind: "choices" }); on text/voice channels the same raise degrades to an enumerated conversational directive. Every question carries an implicit free-textotherescape hatch (mirroring AskUserQuestion's ever-present "Other"), so the visitor can always answer outside the enumerated options.Server-side validation (
validate_choices, shared by the card path's WS handler and the fallback path'ssubmit_interactiontool): every question answered, each selected label offered, single-select takes exactly one pick (label XORother), multi-select one or more; invalid submits return retryable per-questioninteraction_invaliderrors, never a terminal error.ChoicesKindis registered in the defaultInteractionRegistry. The canonical contract lives inspec/interactions/choices.schema.json(Spec / Values / Payload) with conformance fixtures; the other-language servers follow as parity work.@smooai/smooth-operator-web-chat-example@0.0.92
Patch Changes