hello, @billowy-elephant-32063 @gray-monitor-53387 addressed the issue of non displayable artifacts from the ui on local but two solutions were offered. deploying kubernetes locally with something like minio seems like overkill when you just want to use the ui to explore the contents of

.metaflow

. is there an out of the box way to use the ui to explore the contents of

.metaflow

? i am confused on why a notebook has to be created to inspect flows when we could already leverage the ui for this. for ref here are the past threads: https://outerbounds-community.slack.com/archives/C02116BBNTU/p1680844294857829 https://outerbounds-community.slack.com/archives/C02116BBNTU/p1665481436770399

another way to explore the contents stored locally would be to use

metaflow cards

- https://docs.metaflow.org/metaflow/visualizing-results/advanced-shareable-cards-with-card-templates#developing-a-card-template

thanks for the explanation! it would be def a nice feature because you could do so much out of the box. also because you can also check out cards and nbs from the ui, effectively deeming an extra tool like w&b less necessary