Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tools access to environment variables #2435

Open
asc2030 opened this issue Feb 14, 2025 · 1 comment
Open

Tools access to environment variables #2435

asc2030 opened this issue Feb 14, 2025 · 1 comment

Comments

@asc2030
Copy link

asc2030 commented Feb 14, 2025

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.

@sarahwooders
Copy link
Collaborator

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.

export MY_ENV_VAR=.... 
letta server

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

No branches or pull requests

2 participants