Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Allow disabling one plugin's hooks without disabling the plugin

未关闭
#4,958 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
65/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
shell

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

triage

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.

主要语言
Shell
星标
11.2k
派生
1.9k
平均合并
14 小时 16 分钟
30 天内合并 PR
6

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/copilot-cli 的其他 Issue

查看 github/copilot-cli 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。