@hazelnot @kleines_z @clemens no problem! I've found that workaround on the extension's Github page, because I was facing the same issue a while ago