Allow disabling one plugin's hooks without disabling the plugin

Look at the plugin management code, likely in a directory like src/plugin or lib/plugin. Find where hooks are registered and disabled (search for disableAllHooks). The /env command output is mentioned; see how it lists hooks by plugin. Start by understanding the plugin lifecycle and hook registration. A good test is to modify a plugin's hook state and verify the plugin's skills still work.

Please let me disable one plugin's hooks without disabling its skills, agents, or MCP servers.

Why

I run several third-party plugins and want to keep using one plugin's skills. I also want to vet or replace its sessionStart hook without losing those skills.

• Two plugins can inject context at sessionStart, but I want one owner for that context.
• A plugin update can change a hook, and I want to hold that hook until I review it.

Today

• disableAllHooks: true skips hooks from every source, including every plugin.
• copilot plugin disable NAME disables the whole plugin. Its help offers no per-component option.

The only workaround is to patch the plugin's hook manifest locally. That patch drifts or gets overwritten when the plugin updates.

Proposal

A per-plugin hook toggle could leave the plugin's other parts active. Either of these shapes might work:

• A config entry such as "pluginHooks": { "<plugin>": false }.
• A flag such as copilot plugin disable NAME --hooks-only.

Since 1.0.60 (#3871), /env lists hooks by plugin. Please show their disabled state there.

Related

#3697 asks to disable repository hooks for security. This request covers plugin hooks while preserving the plugin's other parts.