Default to the retriever set in config rather than just tavily #1019
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.
Right now if the retriever isn't set in the headers, it defaults to the environment variable RETRIEVER. If that's not set, it defaults to Tavily.
The problem with this is even if the retriever is set in the config, it's completely ignored.
I had no RETRIEVER environment variable set, but I had retriever set in my configs to Bing, Google, etc., and was wondering why I was blowing past all my Tavily API limits...
The current workaround is to manually set the retriever in the headers rather than the config.