Allow disabling one plugin's hooks without disabling the plugin
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 65/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- shell
- Área
- cli, developer-experience
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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: trueskips hooks from every source, including every plugin.copilot plugin disable NAMEdisables 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.
- Lenguaje dominante
- Shell
- Estrellas
- 11.2k
- Forks
- 1.9k
- Merge medio
- 14 h 16 min
- PR fusionados (30 d)
- 6
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/copilot-cli
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
github/copilot-cli#4932 ·
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
github/copilot-cli#4909 ·
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
github/copilot-cli#4906 ·
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
github/copilot-cli#4848 ·
-
area:agents area:mcp
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
github/copilot-cli#4729 ·
Todos los issues de github/copilot-cli
Issues similares
-
Bob Shell support Abiertoenhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
tooling
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
openSUSE/python-rpm-macros#219 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
YunoHost-Apps/adguardhome_ynh#258 ·
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repair Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
ValveSoftware/SteamOS#2829 ·