Closed Propheticus closed 6 months ago
The way that agent calling works is not 1<>1 text to action. There are possibilities where an agent can call the same action twice, call the actions forever in a loop, and other repetitions like that. In fact, on many of the agent tools we have a built-in de-duplicator that prevents this.
You even get this behavior with GPT, so its just an LLM thing. Given the temp is set to 0 this makes sense the requests look the same. That is just an artififact of tool calling, some tools dont have a de-duplicator on them and i believe web-search is one of them
By agent you mean the LLM assuming that role and picking actions? I'm trying to understand, but the issue here seems that the original (very first) query and system instruction telling it to assume the agent role is sent twice. It's not the LLM/agent going in a circle. It did not receive the output of the web browsing and again call a web browse, it received the first "you are a program which picks the...." system prompt again. Due to the temp being 0 it's expected the reply is the same.
Hi, is there a solution for this? Currently agent calls for Bing search are not working due to the same issue using Azure OpenAI as the LLM.
It seems this bug also prevents me from using SearXNG agent in combination with Azure OpenAI.
How are you running AnythingLLM?
Docker (local)
What happened?
Using Docker latest image build (b3f0a413afc2bf3efec4042a158203c76d2b14279adbd29753a37239be1925fc)
Using the agent call feature, results in 2 calls to the LLM provider and twice a function call in JSON is replied back.
This one agent call, was received in LM studio (and responded to) 2 times. LMStudio server logs of POST requests:
Docker logs of AnythingLLM container:
Are there known steps to reproduce?
No response