Skip to content

feat(tools): add support for client-side tools#33

Open
justintime4tea wants to merge 1 commit intomainfrom
feature/client-side-tools
Open

feat(tools): add support for client-side tools#33
justintime4tea wants to merge 1 commit intomainfrom
feature/client-side-tools

Conversation

@justintime4tea
Copy link
Copy Markdown
Collaborator

@justintime4tea justintime4tea commented Mar 25, 2026

This adds the ability for clients to submit a list of client-side tools, via the OpenAI chat completions request spec, and have them "passthrough" to the client instead of being executed "server-side".

Ref: LOG-23583

@justintime4tea justintime4tea requested a review from a team March 25, 2026 18:59
@justintime4tea justintime4tea force-pushed the feature/client-side-tools branch 3 times, most recently from deb8e12 to 761d8ef Compare March 30, 2026 14:58
@justintime4tea justintime4tea enabled auto-merge (rebase) March 30, 2026 14:58
@justintime4tea justintime4tea force-pushed the feature/client-side-tools branch 2 times, most recently from b09e456 to baae71a Compare April 6, 2026 16:53
This adds the ability for clients to submit a list
of client-side tools, via the OpenAI chat completions
request spec, and have them "passthrough" to the client
instead of being executed "server-side".

Ref: LOG-23583
@justintime4tea justintime4tea force-pushed the feature/client-side-tools branch from baae71a to ae6cc3d Compare April 6, 2026 16:53
Copy link
Copy Markdown
Collaborator

@Shearerbeard Shearerbeard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good - as it rebased orchestration we should probably consider organizing this into some of the library types splitting and reorganization - streaming/types.rs already needed a split. I didn't review the docs heavily but this should be noted as a use at your own risk for server side enterprise deployments - exposing client side tools to your agent thats public facing (like our web deployment) could be an attack vector

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants