Skip to main content
H
hpssa
August 8, 2026
Solved

1Password disables developer tools in Microsoft Edge

  • August 8, 2026
  • 2 replies
  • 0 views

1Password has applied an unwanted policy against Edge, disabling devtools if a 1Password popup is injected in the page.

I can’t find the setting to disable this, anyone know?

To reproduce:

  1. Visit a page with a credential or webform that 1Password supports
  2. Open devtools with F12
  3. Click on the 1Password icon in the page

Devtools window is closed, and an error is shown: “Your organisation has blocked the use of devtools on this page”

Note: The org doesn’t block this use, and the org wants to use the feature without having it close mid-diagnosis of issues, losing history in the devtools window we needed (not bitter at all...)

Best answer by 1P_Dave

Hello ​@hpssa! 👋

Thank you for reaching out. I understand that you've been seeing the Developer Tools window close while using 1Password in your browser. I suspect you're running into a new behaviour introduced in Chromium 149. When Developer Tools is open and a force-installed extension managed by your organization is activated, Chromium browsers automatically close the Developer Tools window. You can find the details on the change made in Chromium here: https://github.com/chromium/chromium/commit/e5f8ed77702af17e2df7591b1de5af980e927b21

There are a few different workarounds that your organization can consider: 

  1. Remove the policy that force-installs the 1Password browser extension and have users install it manually instead.
  2. Use the DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailabilityBlocklist policies to enable developer tools for the extension. This will block developer tools on all other pages unless those pages are explicitly added to the allowlist.
  3. Set the DeveloperToolsAvailability policy to 1 to enable developer tools.

 
You can read more about DeveloperToolsAvailability here: DeveloperToolsAvailability: Control where Developer Tools can be used | Chrome Enterprise

I hope that helps.

-Dave

2 replies

1P_Dave
1Password Employee
1P_DaveAnswer
1Password Employee
August 11, 2026

Hello ​@hpssa! 👋

Thank you for reaching out. I understand that you've been seeing the Developer Tools window close while using 1Password in your browser. I suspect you're running into a new behaviour introduced in Chromium 149. When Developer Tools is open and a force-installed extension managed by your organization is activated, Chromium browsers automatically close the Developer Tools window. You can find the details on the change made in Chromium here: https://github.com/chromium/chromium/commit/e5f8ed77702af17e2df7591b1de5af980e927b21

There are a few different workarounds that your organization can consider: 

  1. Remove the policy that force-installs the 1Password browser extension and have users install it manually instead.
  2. Use the DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailabilityBlocklist policies to enable developer tools for the extension. This will block developer tools on all other pages unless those pages are explicitly added to the allowlist.
  3. Set the DeveloperToolsAvailability policy to 1 to enable developer tools.

 
You can read more about DeveloperToolsAvailability here: DeveloperToolsAvailability: Control where Developer Tools can be used | Chrome Enterprise

I hope that helps.

-Dave

H
hpssaAuthor
August 12, 2026

​@1P_Dave - I am incredibly grateful for this response. I’d have never found it. Thank you! Hopefully this post comes up in search results and helps others.

Terms & ConditionsAccessibility statement

©2026 1Password. All rights reserved.
4711 Yonge St, 10th Floor, Toronto Ontario, M2N 6K8, Canada