You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have tool / toolCall schemas for anthropic and open ai and convert between them when switching providers. This is good and should be the goal for new providers however, we don't want to block adding new providers on getting all of the tool / tool call schemas correct right away.
Solution:
Allow for new providers to be added with no tool / tool call schemas in the UI. With the option to always incrementally add them later for a better (switching between providers) UX if necessary.
Effects:
New providers can start as schema-less which means no linting in json tool / tool call editors and no conversion when switching to that provider (just keep the schema from the previous provider).
Details:
Update error handling to show persistent errors when calling subscription or mutation in the playground to allow user to easily see why their call failed (in this case potentially invalid tools) to offer a path to fixing it
keep provider lists exhaustive in tool / tool call conversion schemas but add handling for providers with no schema
Unknown: how do we convert from a schema-provider to a schema'd one
could create a new "empty" (default) tool for that provider (probably a better option)
could remove tools
The text was updated successfully, but these errors were encountered:
We currently have tool / toolCall schemas for anthropic and open ai and convert between them when switching providers. This is good and should be the goal for new providers however, we don't want to block adding new providers on getting all of the tool / tool call schemas correct right away.
Solution:
Allow for new providers to be added with no tool / tool call schemas in the UI. With the option to always incrementally add them later for a better (switching between providers) UX if necessary.
Effects:
New providers can start as schema-less which means no linting in json tool / tool call editors and no conversion when switching to that provider (just keep the schema from the previous provider).
Details:
The text was updated successfully, but these errors were encountered: