# Disable DevTools

> Disable developer tools and remote inspection using a License capability plus an explicit EP switch.

Source: https://console.getchrovia.com/en/docs/sdk-disable-devtools

**Entitlement:** `disableDevTools`. **Configuration:** `internal.disable_devtools`. No JavaScript API is needed.

## Enable

Place this in the instance's [Extended Preferences](https://console.getchrovia.com/en/docs/sdk-extended-preferences) before startup. Merge it into any existing `internal` object, and re-sign if `signedExtendedPrefs` is required:

```json
{
  "internal": {
    "disable_devtools": true
  }
}
```

Both the entitlement and boolean `true` are required. Missing, false, or incorrectly typed values do not enable the restriction. Granting the License capability alone leaves DevTools unchanged.

## Behavior and testing

DevTools, Inspect actions, keyboard and menu entry points, and remote inspection are disabled. This is not merely a hidden toolbar button: do not expect CDP debugging to remain available.

Launch a test instance and try F12, Inspect, the developer-tools menu, and the remote inspection workflow you deploy. Do not enable this on the instance used to debug a Provision Service Worker or connect an automation client through CDP.

## Disable or diagnose

Set the field to `false` or remove it, re-sign when required, and fully restart. Do not edit a signed EP without updating its signature. Invalid EP is not a supported way to disable a single setting; it blocks the configuration store.

If DevTools still cannot open with this feature off, inspect Chromium policy and other launch restrictions. This capability adds a restriction; it does not override existing policies to permit debugging. For visual password restrictions, see [password reveal block](https://console.getchrovia.com/en/docs/sdk-password-reveal-block).