-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LLM return non exist action in predefined list #1134
Comments
I was never able to reproduce
Guess the LLM I've tried were not "weak" enough.
|
I still cannot reproduce it locally. I have no chance to see the true response. Our code didn't log response, so no user can provide it. If some one can provide the true error |
I found https://www.youtube.com/watch?v=RJ6NN8Y-xok&ab_channel=OfirPress very worth watching. At 18:58, the author mentioned that they had to emphasize the current directory the agent is on, otherwise it would often mess up. This redundant piece of information seemingly helps the LLM strengthen its memory. That being said, apparently powerful LLMs have no problem of remembering what actions are legal. Maybe you want to tune prompt only for "very weak" LLMs, but we don't have a framework to tune prompt per LLM (group) yet. |
Yeah, I also see this case. This is what trigger me idea. I wonder whether add some redundant info in prompts can be helpful to solve it. |
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
What problem or use case are you trying to solve?
Maybe user proposed problem like
in #718, #1064, #1126. I should better figure out a way to improve it, or find a workaround to pass it.
Because it depends on the LLM response, I am still trying to find a way to reproduce it. Want to get the error LLM response to do futher investigation.
Describe the UX of the solution you'd like
Do you have thoughts on the technical implementation?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: