RAG Support and Plugin support more generally

[skyler14]

This is a bit of a two parter question, is there a way to connect this to a RAG easily, or extensions to connect with RAG like anyscale/pinecone/vertex/langchain?

More broadly is there any easy way to extend morphic, like a scaffolding for plugin system or boilerplate? If there isn't yet could you guys identify a entry point for building extensions, modules, and settings. Maybe like if I wanted to create a section like "Images" and "Sources".

If a bit of work could be done to support extensions I'd be interested in building plugins based on morphic.

Examples of Add-Ons that morphic would largely benefit from:
RAG Lookup
Google style pre-built answers saved in RAGs/DBs (or possibly even entire mini markdown/html widgets)
RAG Reference (let you see where in source documents/resources a certain part of the RAG knowledge came from)
Image Generation
Videos Sources (and Video to Transcription built on top of that)
Answer Router (looks at links and references in Answer and then generates any subsections that would fit the content type)
Git visualizer for editing code (bit outside the standard use case here)

I think morphic really has some crazy potential and extensibility to let the community explore how to build on top it would benefit everybody alot.

[miurla]

Thank you. That's great content.

Currently, there is no foundation for building plugins. As an entry point, since Agents have tools, adding tools would allow for functions beyond search. However, it's not in a form that can be easily added on, but I'm thinking of building those. In terms of image, it's like the Assistant settings for the OpenAI Assistant API. Additionally, I plan to generate components that match the tools.

So, as an answer, there are plans to support Rag and Plugin (Tools) Support.
However, this is just the current plan, and it's undecided when or at what timing it will be implemented.

[skyler14]

Ok, that's useful information. If the boilerplate to get tools is built out I think it could compound rate of growth since a tool that connects to RAG or say a github repo connector util could basically allow morphic to help build more morphic. This feature would be a determining factor for me to divert dev resources to start building plugins as well.