imbajin commented on issue #183: URL: https://github.com/apache/incubator-hugegraph-ai/issues/183#issuecomment-2693243409
> I see, so then I think it's feasible to side with CrewAI and build further with a manual implementation of the other libraries. I also think that once the features are fully implemented with crewAI, we can isolate some items for optimizing the performance using Agno's principles. CrewAI here, being the preference since it has far more to offer as compared to Agno and its primary strength being its efficiency. > > Especially since we have to handle L1-LN queries sooner or later, we'll iteratively improve it using the others (Agno, LlamaIndex, etc.) Any suggestions of where we can start with the implementation of the demo, because it would be best to test it out first before finalizing the idea? [@imbajin](https://github.com/imbajin?rgh-link-date=2025-03-03T02%3A50%3A38.000Z) @Kryst4lDem0ni4s As for how to try it out, I think you can follow the general process below (for reference only): 1. First, fully understand the current reading process(Next is the writing process), including the `text2gql` pattern (simple)+extracting keywords ->matching vid -->BFS(multistep) to look up subgraph pattern. Of course, it would be even better if we improved this documentation to clarify everyone's previous text clearer 2. Understanding our current `Pipeline` design, it is relatively simple, just a multi-step separation similar to a factory design pattern(fixed) 3. Try the flow part of the `crewai` and write a simple demo to be familiar with its usage (there is no need to introduce the entire crew design at this time) 4. Then, combining with our GraphRAG process, we will attempt to introduce a minimal agent designed crewai example and simulate it as simply as possible 5. Then checkout a new branch to see how our current version integrates with minimal changes in architecture, and execute it step by step to avoid making too many modifications at once that are difficult to debug 6. ..... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
