-
Notifications
You must be signed in to change notification settings - Fork 96
Description
LightAgent currently supports memory capabilities through custom implementations like mem0, which is excellent. However, many enterprise users already have existing vector database setups (Pinecone, Weaviate, Milvus, Chroma, etc.) for their knowledge bases and would benefit from direct integration options.
Proposed Solution
I'd like to request support for connecting LightAgent to existing vector databases through a standardized interface. This would allow users to:
- Leverage their existing knowledge bases without migrating data
- Use their preferred vector database technology
- Maintain consistent memory across different agent frameworks
Implementation Suggestions
- Create an abstract
VectorStoreinterface class that different database connectors can implement - Include basic connectors for popular vector databases (similar to how
mem0offers Qdrant support) - Allow passing custom vector DB instances to the agent during initialization
- Document best practices for vector dimensions and embedding models compatibility
Example Usage (Concept)
from LightAgent import LightAgent
from my_vector_db_connector import MyVectorDB
# Initialize custom vector DB connection
vector_db = MyVectorDB(connection_params)
# Pass to agent
agent = LightAgent(
model="deepseek-chat",
api_key="your_api_key",
base_url="your_base_url",
vector_store=vector_db
)Benefits
This enhancement would make LightAgent more accessible to enterprise users with existing AI infrastructure and create a more flexible integration path for organizations with specific database requirements or compliance needs.
Additional Context
I've been using LightAgent in several projects and find it incredibly well-designed. This addition would help our team standardize on LightAgent across more use cases.