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
Is your feature request related to a problem? Please describe.
When using tools, it would be useful to be able to access env vars. I have seen there is a way to pass this agents via the API, but I don't see why the tool scripts themselves can't access env vars directly to simplify this process.
Describe the solution you'd like
Similar to how static site generators work like Astro or Gastby, being able to have specific env vars that start with "TOOL_" (or similar) accessible to the tool scripts will make integration with other systems much easier to manage.
Describe alternatives you've considered
I have looked at tool_exec_environment_variables, but this doesn't seem to be ideal when you potentially have multiple agents using the same key that needs to be replaced.
The text was updated successfully, but these errors were encountered:
Hi @asc2030 - we are working on adding improved configurability of the tool execution environment. However I believe you should be able to set env vars when you run the server, e.g.
Is your feature request related to a problem? Please describe.
When using tools, it would be useful to be able to access env vars. I have seen there is a way to pass this agents via the API, but I don't see why the tool scripts themselves can't access env vars directly to simplify this process.
Describe the solution you'd like
Similar to how static site generators work like Astro or Gastby, being able to have specific env vars that start with "TOOL_" (or similar) accessible to the tool scripts will make integration with other systems much easier to manage.
Describe alternatives you've considered
I have looked at tool_exec_environment_variables, but this doesn't seem to be ideal when you potentially have multiple agents using the same key that needs to be replaced.
The text was updated successfully, but these errors were encountered: