What
A new hook source type policySettings is recognized in the hook source registry. It joins userSettings, projectSettings, localSettings, pluginHook, sessionHook, and builtinHook.
Details
- Represents enterprise managed settings delivered out-of-band by an administrator; displayed to users as
"managed"(short),"Managed"(header), and"enterprise managed settings"(long form) in the settings/hooks UI - Unlike
userSettings,projectSettings, andlocalSettings,policySettingsis always included in the allowed sources list regardless of the--allow-setting-sourceCLI flag (it is force-added alongsideflagSettingsin the source filter) policySettings.disableAllHooks = truedisables all hooks entirely — even plugin hooks — across all sourcespolicySettings.allowManagedHooksOnly = truerestricts hook execution to onlypolicySettings.hooks; user, project, and local hooks are silently ignored for the session- If
qi().disableAllHooksistruebutpolicySettings.disableAllHooksis nottrue, hooks from managed settings still run (the setting overrides only non-managed hooks) - Hooks declared under
policySettings.hooksare therefore the only hooks an administrator can guarantee will always run; user-side hooks can be suppressed without touching the user's own settings files - In hook priority sorting, hooks sourced from
policySettingsshare bucket 999 withpluginHookandbuiltinHook, making them sort after user/project/local hooks in the display
Evidence
Hook source labels (search for "policySettings" in hook source map at new TJt variable); hook resolution logic (search for Lzi, iOe, QX, allowManagedHooksOnly, disableAllHooks)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.