Skip to content
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

[Feature Request]: Agent supports global memory #4521

Open
1 task done
TeslaZY opened this issue Jan 17, 2025 · 2 comments
Open
1 task done

[Feature Request]: Agent supports global memory #4521

TeslaZY opened this issue Jan 17, 2025 · 2 comments
Assignees
Labels

Comments

@TeslaZY
Copy link
Contributor

TeslaZY commented Jan 17, 2025

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

@KevinHuSh
Copy link
Collaborator

We typically use multiple categorizes which represents like a tree. The scene name is on sub-tree of the recommend a product node .

@TeslaZY
Copy link
Contributor Author

TeslaZY commented Jan 17, 2025

In some cases, it is not suitable to use sub-tree.

[I hope the agent can divide the two problems into one category according to the context]

User: Recommend me a GPU

Agent: Please tell me the GPU usage scenario you need.

User: machine learning

Agent: return {the product information of machine learning GPU from the knowledge base or database}

[I hope it is divided into two categories]

User: machine learning

Agent:return {Information from the knowledge base or search engine}

Therefore, agent memory and global context may be necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants