Yes, we’re aware of this need and have a plan for it. The divide in capabilities between “in your library” and “not in your library” is mostly artificial, and results from the history of this project more than conscious design choices.
There is a substantial re-engineering effort involved in addressing this, because a huge body of code sits on top of this structure, so it will take a while, but we are planning to do it at some point.