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
Users may have custom secrets and api keys they want Openhands to access; we should have some way to allow users to specify these values through the UI and store it in their settings.
Describe the UX of the solution you'd like
Add a section to the settings modal. User could add new entries with secret name and value.
Do you have thoughts on the technical implementation?
We should create a unified settings store for users
We already export $GITHUB_TOKEN in the remote runtime when we see the agent attempting to use $GITHUB_TOKEN. We would do something similar for other user secrets.
Describe alternatives you've considered
Additional context
cc @tofarr who may be working on this
The text was updated successfully, but these errors were encountered:
What problem or use case are you trying to solve?
Users may have custom secrets and api keys they want Openhands to access; we should have some way to allow users to specify these values through the UI and store it in their settings.
Describe the UX of the solution you'd like
Add a section to the settings modal. User could add new entries with secret name and value.
Do you have thoughts on the technical implementation?
We should create a unified settings store for users
We already export
$GITHUB_TOKEN
in the remote runtime when we see the agent attempting to use$GITHUB_TOKEN
. We would do something similar for other user secrets.Describe alternatives you've considered
Additional context
cc @tofarr who may be working on this
The text was updated successfully, but these errors were encountered: