-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Recent tags change causes AttributeError: 'str' object has no attribute 'value' on initialize_agent call #6756
Closed
1 of 14 tasks
Labels
01 bug
Confirmed bug
Comments
yes i also got this error too. Apparently we have to use AgentType.ZERO_SHOT_REACT_DESCRIPTION , the old way of using just strings has been changed . At the very least they could have shown an exception error instead of this jargon. |
agree!the same to me! |
Will land a fix. Thanks for raising this! |
Merged
hwchase17
pushed a commit
that referenced
this issue
Jun 26, 2023
Fix tags change that broke old way of initializing agent Closes #6756
Thank you,it's working now. |
kacperlukawski
pushed a commit
to kacperlukawski/langchain
that referenced
this issue
Jun 29, 2023
Fix tags change that broke old way of initializing agent Closes langchain-ai#6756
aerrober
pushed a commit
to aerrober/langchain-fork
that referenced
this issue
Jul 24, 2023
Fix tags change that broke old way of initializing agent Closes langchain-ai#6756
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System Info
Who can help?
@vowelparrot
https://github.com/hwchase17/langchain/blob/d84a3bcf7ab3edf8fe1d49083e066d51c9b5f621/langchain/agents/initialize.py#L54
Information
Related Components
Reproduction
Fails if agent initialized as follows:
With
Expected behavior
Expected to work as before where agent is specified as a string (or if this is highlighting that agent should actually be an object, it should indicate that instead of the error being shown).
The text was updated successfully, but these errors were encountered: