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] Add GraphDBBlock to LongtermAgentMemory and add GraphDBMemory #846

Open
1 of 2 tasks
lightaime opened this issue Aug 20, 2024 · 0 comments · May be fixed by #851
Open
1 of 2 tasks

[Feature Request] Add GraphDBBlock to LongtermAgentMemory and add GraphDBMemory #846

lightaime opened this issue Aug 20, 2024 · 0 comments · May be fixed by #851
Assignees
Labels
enhancement New feature or request Memory P1 Task with middle level priority
Milestone

Comments

@lightaime
Copy link
Member

lightaime commented Aug 20, 2024

Required prerequisites

Motivation

We have supported GraphRAG. However, knowledge graphs are not used in AgentMemory yet. We many want to introduce GraphDBBlock to LongtermAgentMemory and add GraphDBMemory.

https://github.com/camel-ai/camel/blob/master/camel/memories/agent_memories.py

An example on how to use Neo4jGraph for GraphRAG here:

https://colab.research.google.com/drive/1meBf9w8KzZvQdQU2I1bCyOg9ehoGDK1u#scrollTo=l4VANToobUzu

A couple things to be discussed:

  • What is the default structure of the LongtermAgentMemory? Should we always have both VectorDBBlock and GraphDBBlock or allow different combinations?
  • Should we allow user to load a pre-built knowledge graph?
  • Should we allow agent to automatically convert chat messages into knowledge graphs?
  • How to score, retrieve and decide whether to use the retrieved results?
  • How to combine to retrieved KGs with vector_db_retrieve and chat_history?

Solution

No response

Alternatives

No response

Additional context

No response

@lightaime lightaime added enhancement New feature or request Memory labels Aug 20, 2024
@lightaime lightaime self-assigned this Aug 20, 2024
@Wendong-Fan Wendong-Fan added call for contribution P1 Task with middle level priority labels Aug 20, 2024
@mrsbeep mrsbeep self-assigned this Aug 20, 2024
@mrsbeep mrsbeep linked a pull request Aug 21, 2024 that will close this issue
13 tasks
@Wendong-Fan Wendong-Fan added this to the Sprint 11 milestone Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Memory P1 Task with middle level priority
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants