Closed TanGentleman closed 6 months ago
The way I see it moving forward is one of two ways:
1) Chains as an API endpoint. These can be full RAG pipelines with lots of in between steps. These would be targeted towards developers OR as a server interacting with a local UI. I would have to invest some time in making some proof-of-concept workflows before pouring hours into the architecture for the API.
2) Plug-and-play with a UI like Cohere Toolkit. I really that project and will draw inspiration from it if the project goes in that direction.
3) Focus solely on studying people's existing workflows and creating custom tools for those. This will not require the same number of hours of polishing/troubleshooting/maintenance, and presents immediate value. I'm leaning towards this one.
I'm going to cross off number 2 from the above list. Definitely having the most fun with a mix of 1 and 3. It definitely seems to be treading into organizing agentic workflows. I'll make a new issue as this is no longer really in the scope of making a README.
Finalize a direction and primary use case for the project. For now, I like the RAG chat as the main selling point.