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
Describe the bug
When the search api returns empty results, it is being passed to llm directly to generate report. And in absence of no context, the llm is responding that it cannot generate report. Since we are directly streaming the content to the websocket client, which might be directly used in ui, this response seems irrelevant.
Expected behavior
I think if the retriever is giving no search results, this should have been logged as error and then generate empty report.
Screenshots
The text was updated successfully, but these errors were encountered:
It's a fair point - we'll need to meditate on it.
What if the message says something like: "I couldn't find context related to your query - please try another search or contact your web admin if you believe this is an error. Sincerely, your AI Research Agent"
Describe the bug
When the search api returns empty results, it is being passed to llm directly to generate report. And in absence of no context, the llm is responding that it cannot generate report. Since we are directly streaming the content to the websocket client, which might be directly used in ui, this response seems irrelevant.
Expected behavior
I think if the retriever is giving no search results, this should have been logged as error and then generate empty report.
Screenshots

The text was updated successfully, but these errors were encountered: