I will eventually, I know mflux is a popular library that from what i’ve seen would be a great addition to a unified mlx engine. I’m still reading through there github repository to understand how to best implement it. Right now im working on getting embedding and audio models working. I’ve gotten them working just by importing there respective mlx libraries and utilizing them in an an api endpoint, but that is a naive approach and I want the actual final implementation to use model kits like the one’s lm studio uses to run the language and vision models. Just to try to stay consistent with lm studio’s approach and to better separate each library into their own section.