🦋 New version release

[brentrager]

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.39.0

Minor Changes

• d41643e: File transfer (TS server): implement the PR protocol: file-transfer contract (send_message.files[] + send_file directive) #342 contract to Rust parity. send_message now parses images[] and files[]: images are attached to the turn's user message as OpenAI image_url content parts (via a withUserImages request-body wrapper, since the published core takes a plain-string message and reuses it for retrieval), while files are surfaced — never sent to the model — on a new per-turn ToolContext. A new optional toolProvider seam (mirroring the Rust ToolProvider) hands host tools that context, including a directive sink; a host tool that writes ctx.directive (e.g. a send_file directive) has it drained onto eventual_response.directive (last-write-wins). All attachment parsing is fail-soft. The client SDK's generated protocol types gain the images/files request fields and the directive response field.

@smooai/smooth-operator-server@1.6.0

Minor Changes

• d41643e: File transfer (TS server): implement the PR protocol: file-transfer contract (send_message.files[] + send_file directive) #342 contract to Rust parity. send_message now parses images[] and files[]: images are attached to the turn's user message as OpenAI image_url content parts (via a withUserImages request-body wrapper, since the published core takes a plain-string message and reuses it for retrieval), while files are surfaced — never sent to the model — on a new per-turn ToolContext. A new optional toolProvider seam (mirroring the Rust ToolProvider) hands host tools that context, including a directive sink; a host tool that writes ctx.directive (e.g. a send_file directive) has it drained onto eventual_response.directive (last-write-wins). All attachment parsing is fail-soft. The client SDK's generated protocol types gain the images/files request fields and the directive response field.

@smooai/smooth-operator-web-chat-example@0.0.51

Patch Changes

• Updated dependencies [d41643e]
  • @smooai/smooth-operator@1.39.0