| > One thing I really care about is extensibility Totally makes sense! We've defined simple `Connector`, `Tool` and (soon) `Agent` interfaces to make it easy to plug in your own implementations/apps. If you wanted, you could just use Langchain under our Agent class to build arbitrary flows. Additionally, the main chat is created from a series of `Renderer` components, and it should be easy to build your own. Do you think that's in-line with what you're thinking of, or do you want to build outside of those confines? > canvas mode and scheduled actions Yes, writing and recurring are two big areas we want to tackle next year. > The main thing I really care about is voice mode Interesting. Why do you think that is? |
It definitely sounds good. Of course it's hard to anticipate what interfaces new features will require, it probably won't always be possible to integrate new features with a generic plugin (voice mode is most likely such a feature), but if the code is well architected, this should be okay.
> Interesting. Why do you think that is?
Writing has a lot of friction to me. It's much more comfortable for me to provide context through verbal rambling, which LLMs are great at processing. I like to research stuff and throw around ideas while pacing, doing chores or just lying with my eyes closed.
Unfortunately I just discovered that I won't be able to run Onyx on my low powered home server anyway (https://docs.onyx.app/deployment/getting_started/resourcing#...). I understand that a Vector database requires significant resources to run, but I wish there was a version without it.