console logs: unable to filter out 1password logs in local development

As a front end developer, I have a feature request: the ability to turn off logs from the 1password extension. This could be just a checkbox to enable/disable logs, maybe a developer mode for debugging implementation which enables logs, anything! Maybe logging them as `console.debug` instead of `console.log`? A checkbox for disabling logs on `localhost` only?

I love 1password, don't get me wrong. But the logs have been the bane of my existence when working on any web app involving authentication, because there's no way to filter out the logs.

Example output:

background.js:80 📤 Sending <NmLockState> message to native core <2920926948>
11:00:39.169 background.js:80 📥 Received message <NmLockState> from native core <2920926948>. Duration: 4.3ms
11:00:54.167 background.js:80 📤 Sending <NmLockState> message to native core <1746240738>
11:00:54.171 background.js:80 📥 Received message <NmLockState> from native core <1746240738>. Duration: 4.6ms
11:01:09.172 background.js:80 📤 Sending <NmLockState> message to native core <4161527562>
11:01:09.183 background.js:80 📥 Received message <NmLockState> from native core <4161527562>. Duration: 11ms
11:01:21.119 background.js:80 📤 Sending <NmLockState> message to native core <951950119>
11:01:21.151 background.js:80 📥 Received message <NmLockState> from native core <951950119>. Duration: 31.7ms
11:01:24.171 background.js:80 📤 Sending <NmLockState> message to native core <2174341925>
11:01:24.176 background.js:80 📥 Received message <NmLockState> from native core <2174341925>. Duration: 5.8ms
11:01:39.173 background.js:80 📤 Sending <NmLockState> message to native core <1407972505>
11:01:39.186 background.js:80 📥 Received message <NmLockState> from native core <1407972505>. Duration: 12.6ms
11:01:54.171 background.js:80 �� Sending <NmLockState> message to native core <2421987558>
11:01:54.184 background.js:80 📥 Received message <NmLockState> from native core <2421987558>. Duration: 13.1ms
11:02:09.172 background.js:80 📤 Sending <NmLockState> message to native core <630129950>
11:02:09.188 background.js:80 📥 Received message <NmLockState> from native core <630129950>. Duration: 15.8ms
11:02:21.119 background.js:80 📤 Sending <NmLockState> message to native core <964956985>
11:02:21.123 background.js:80 📥 Received message <NmLockState> from native core <964956985>. Duration: 4.5ms
11:02:24.171 background.js:80 📤 Sending <NmLockState> message to native core <3234675529>
11:02:24.177 background.js:80 📥 Received message <NmLockState> from native core <3234675529>. Duration: 5.8ms
11:02:39.170 background.js:80 📤 Sending <NmLockState> message to native core <714895378>
11:02:39.176 background.js:80 📥 Received message <NmLockState> from native core <714895378>. Duration: 5.5ms
11:02:54.171 background.js:80 📤 Sending <NmLockState> message to native core <1997105720>
11:02:54.178 background.js:80 📥 Received message <NmLockState> from native core <1997105720>. Duration: 7.5ms
11:03:09.173 background.js:80 📤 Sending <NmLockState> message to native core <1243253266>
11:03:09.199 background.js:80 📥 Received message <NmLockState> from native core <1243253266>. Duration: 26.2ms
11:03:21.175 background.js:80 📤 Sending <NmLockState> message to native core <3734071001>
11:03:21.181 background.js:80 📥 Received message <NmLockState> from native core <3734071001>. Duration: 6.5ms
11:03:24.171 background.js:80 📤 Sending <NmLockState> message to native core <1854610928>
11:03:24.173 background.js:80 📥 Received message <NmLockState> from native core <1854610928>. Duration: 2.6ms
11:03:39.171 background.js:80 📤 Sending <NmLockState> message to native core <3181823558>
11:03:39.176 background.js:80 📥 Received message <NmLockState> from native core <3181823558>. Duration: 4.7ms
11:03:54.171 background.js:80 📤 Sending <NmLockState> message to native core <3797715197>
11:03:54.180 background.js:80 📥 Received message <NmLockState> from native core <3797715197>. Duration: 8.8ms
11:04:09.171 background.js:80 📤 Sending <NmLockState> message to native core <2885493011>
11:04:09.177 background.js:80 📥 Received message <NmLockState> from native core <2885493011>. Duration: 5.5ms
11:04:18.049 background.js:80 📤 Sending <NmLockState> message to native core <386599336>
11:04:18.052 background.js:80 📥 Received message <NmLockState> from native core <386599336>. Duration: 3.2ms
11:04:24.171 background.js:80 📤 Sending <NmLockState> message to native core <3057763534>
11:04:24.177 background.js:80 📥 Received message <NmLockState> from native core <3057763534>. Duration: 6.6ms
11:04:39.171 background.js:80 📤 Sending <NmLockState> message to native core <3449831082>
11:04:39.174 background.js:80 📥 Received message <NmLockState> from native core <3449831082>. Duration: 3.1ms

I've also found these other relevant posts on the same issue with no solution:

• How to silence 1Password noise in the browser console | 1Password Community 
• Chrome extension background.js logs and/or errors in console | 1Password Community
• Sending &lt;NumLockState&gt; messages | 1Password Community