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
In the Plugin Store installation dialogue a user can add an API Keys.
This is not possible with tools for agents as I understand.
I propose adding user provided API Keys for Tools. The dialogue can pop up when the user wants to add the tool to and agent and no Keys is present from .env.
More details
I understand users should mostly use actions, but for some complex actions it's still nice to have the tool just to be installed rather than copy/pasting/sharing OpenAPI code.
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What features would you like to see added?
In the Plugin Store installation dialogue a user can add an API Keys.
This is not possible with tools for agents as I understand.
I propose adding user provided API Keys for Tools. The dialogue can pop up when the user wants to add the tool to and agent and no Keys is present from .env.
More details
I understand users should mostly use actions, but for some complex actions it's still nice to have the tool just to be installed rather than copy/pasting/sharing OpenAPI code.
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: