Remove developer warning

[NicholasKK]

This is a tutorial, not an issue. I'm not sure where to post this under the project.

You can disable the extension developer warning as stated in extension help by adding "--silent-debugger-extension-api" parameter to the shortcuts. The issue with this is that you have to add it to all shortcuts and If you have created an web app, the parameter won't work, because it resets each time you reboot. Also, this won't work if you have allowed chrome or edge to autorun after computer boots up, because the registry value resets after each reboot.
There is also another way to disable the warning, which works for all shortcuts, apps created through Chrome and Edge and even the initial auto startup.

You can disable it by adding the following key to registry:

Registry Hive | HKEY_LOCAL_MACHINE (for all users) or HKEY_CURRENT_USER (for current user)
Registry Path | Software\Policies\Google\Chrome\ExtensionInstallForcelist
Value Name | {number} (example: **1** or if there is already a key, type a number in incremental order)
Value | **ncbknoohfjmcfneopnfkapmkblaenokb**

In Edge Chromium you can do the same, just in the following registry path:

Registry Path | Software\Policies\Microsoft\Edge\ExtensionInstallForcelist

[z0ccc]

Cool! I will add this to the readme. Thanks

[NicholasKK]

You are very welcome. You may also add that if a user decides to remove the extension after adding the above registry key, they have to delete the key before being able to remove the extension.

and Thank you for developing the extension.

[NDevTK]

Instead of requesting access to all urls and trying to find a way to attach to targets that can be created at anytime before any code runs and ignoring security warnings it would be better for this usage to be part of https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/privacy

Would be nice feature :)

[askusWT]

I like NicholasKK's proposal, but I'm going to caution the effort-reward going after it.

1. It's a good solution, for Windows.
2. It's not possible on Mac or Linux. These both need a command-line flag via the terminal (though I guess .desktop would be the shortcut equivalent). There's also a bit of potential port conflict to work through
3. A Linux-enabled Chromebook can make the point above work, providing the user is running Lacros in the container.
4. If not, there is no solution (currently) for a Chromebook running regular chrome outside of the container (though when Lacros is formally launched there may be).

Describing the problem already took far too long to type. That always gets me to wonder, is doing something about it really worth it?
Which use case needs this on all the time? Maybe I'm missing something because I found myself a really helpful debugging shortcut with Vytal that I would never want to use permanently.

I'm reminded of an old boss whose adage was, "the more they ask, the more we've overcomplicated. How do we do less?" His solution would be:

1. Highlight the potential debugging annoyance so people are aware, anticipating and not logging issues. Preferably make it a good thing they want.
2. Add a toggle for Vytal on the extension tool bar so it can be triggered easily when needed, or as I suspect is an unlogged issue, accidentally cancelled.

Make it a Feature

You could supplement the FAQs and Chrome description (with something better than the collage I've mocked up to demonstrate ⬇) to ensure no new user misses that the experience is invasive. With a little marketing flourish the debug warning could even become a feature to alert the user that the tool is still being used.

Add a Toggle

The code for a simple on-off toggle on the extension is available through any number of equivalent extensions facing analogous problems.

Just my take, but I hope helpful, even if just to remove some short-term issue pressure.