-
-
Notifications
You must be signed in to change notification settings - Fork 632
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
Why does the Executor.Call function not pass the opts parameter to Agent.Plan? #353
Comments
I agree that options should be threaded through to Plan. I have #463 filed and I think this is an example of something that should be revamped. Given that upstream is planning/prepping for 0.2.0, I think some new design thinking around not just the interface to the agents package but implementation details like this should be fixed. Do you want to propose a change to add variadic options to Plan() and pass it through here? |
Yes, in my local reference, I have appended variadic parameters to Plan(). And I agree with your point, I am looking forward to the release of version 0.2.0. |
Yes, passing is invalid when I use chains.WithTemperature(0.95) |
When I follow the test to use agent
I find that i cannot paas param like StopWords/MaxTokens to openai llm
when i follow the code, i find that the Executor.Call function not pass the opts parameter to Agent.Plan
which causes that the param i have set is useless
So, Why does the Executor.Call function not pass the opts parameter to Agent.Plan? Is there some reason?
The text was updated successfully, but these errors were encountered: