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
Is there an existing issue for the same feature request?
I have checked the existing issues.
Is your feature request related to a problem?
If Agent uses the Category node, it will sometimes divide the user's questions into different categories, but in fact, the two problems are contextual. For example, the first question requires agent to recommend a product. After interacting with llm, llm prompts you to need more information, such as the usage scenario of the product. At this time, if I directly reply to the use scenario name, Category will divide the scene name and the first question "recommend a product" into two categories. Then the agent will follow different flow branches and make memory switching, which is different from the previous tag.
Describe the feature you'd like
We can consider adding the global agent memory to support better problem classification, question answer and other scenario performance, and avoid the context conversion problems caused by the switching branch caused by Category. Agents should always behave like the same person for a session, instead of looking like schizophrenic now.
Describe implementation you've considered
No response
Documentation, adoption, use case
- Add the global agent memory
Additional information
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for the same feature request?
Is your feature request related to a problem?
Describe the feature you'd like
We can consider adding the global agent memory to support better problem classification, question answer and other scenario performance, and avoid the context conversion problems caused by the switching branch caused by Category. Agents should always behave like the same person for a session, instead of looking like schizophrenic now.
Describe implementation you've considered
No response
Documentation, adoption, use case
- Add the global agent memory
Additional information
No response
The text was updated successfully, but these errors were encountered: