Tools not configured properly via CLI during `make-first run` when inserting API Key env variables
heaversm opened this issue · 2 comments
What is the issue?
When navigating to the web interface (localhost:4000) and clicking on tools after going through the local install and providing my API keys (Tavily / Wolfram, etc): each tool shows an error when hovering over the (i) info icon:
Additional information
No response
I think that this is a UI bug, not an actual issue with the API keys- it seems to be retrieving results from the internet. I tested Wikipedia as well, and while it says Error: LangChainWikiRetriever not available., the details on a chat result with Wikipedia checked reveal sources from wikipedia.
I can also confirm that these API keys are present in the root .env file, so the CLI is writing them properly.
It appears that tools.py is looking for whether each tool is_available, but you can hard code this to be True, and the error will still show, e.g.:
#is_available=LangChainWikiRetriever.is_available(),
is_available=True,
If you go to backend/tools/lang_chain.py, in the class LangChainWikiRetriever they are actually hard coding True for this by default:
@heaversm Certain tools have their is_available() method hardcoded to return True when no API keys are required, but indeed it does look like some bug with the frontend. I'll raise this issue internally