disable tools based on provided env variables #165
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
January 27, 2025 13:12
… env variable is not given
|
Someone is attempting to deploy a commit to the Neur Team on Vercel. A member of the Team first needs to authorize it. |
…nv variable is not given
briang123
reviewed
Jan 28, 2025
briang123
approved these changes
Jan 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #85
disable tools based on provided tool names in NEXT_PUBLIC_DISABLED_TOOLS env variable or if a tool has a requiredEnvVar then you can disable that tool by simply not providing that env variable or making it's value an empty string.
The screenshot below shows dynamically disabling tools, by changing env variable