The reason to use Native Messaging is because you want to access some native binary on the users machine. Usually the extension author is also the creator of that binary. This is how password managers work, for example. With something like 1Password, you visit their website and download an installer. This installer has the native binary, places it in a well-known location and configures permissions. Then they tell you to go to the Chrome Web Store to install their extensions. The extension knows where the binary is and starts interacting with it via Native Messaging. I was wondering if Plasmo might be able to tackle that problem - packaging, signing, downloading, authorizing, native binaries (cross-os as well) and make it seamlessly work with what I've built in Plasmo.