Feature Request: Global Hooks Configuration with UserPromptSubmit, Stop, and Notification Events

[jie-meng]

Problem Statement

Currently, GitHub Copilot's hooks implementation has significant limitations compared to similar AI coding assistants like Claude Code and Cursor:

1. No global configuration: Hooks must be configured per repository via .github/copilot-hooks.json, requiring repetitive setup across projects
2. Limited event types: Only basic Start hooks are supported, missing critical lifecycle events
3. Poor developer experience: Cannot set up system-wide preferences for workflow automation

Use Case

I want to play different audio notifications to get immediate feedback during AI interactions:

• UserPromptSubmit: When I submit a prompt to Copilot (AI starts working)
• Stop: When Copilot finishes generating the response
• Notification: When Copilot asks a question or needs my input (different sound to distinguish from completion)

This helps maintain awareness of AI activity without constantly monitoring the terminal, especially during long-running operations or when multitasking.

Comparison with Competitors

Claude Code (docs):

• ✅ Global hooks configuration in user settings
• ✅ Supports UserPromptSubmit, Stop, Notification events
• ✅ Simple setup without per-repository configuration

Cursor (docs):

• ✅ Global hooks configuration
• ✅ Supports multiple lifecycle events including completion and user interaction
• ✅ User-level preferences

GitHub Copilot CLI (docs):

• ❌ Repository-level only (.github/copilot-hooks.json)
• ❌ Only userPromptSubmitted event supported
• ❌ No global/user-level configuration
• ❌ Missing Stop and Notification events
• ❌ And I tried to configure in my repository, never success to play sound when I submit a a prompt

Proposed Solution

1. Add global hooks configuration

   • Support user-level hooks in ~/.config/copilot/hooks.json (or OS-equivalent)
   • Allow global hooks to be overridden by repository-specific hooks when needed

2. Add essential lifecycle events

   • UserPromptSubmit: Triggered when user submits a prompt
   • Stop: Triggered when Copilot completes the response
   • Notification: Triggered when Copilot asks for user input/clarification

3. Example configuration (desired syntax):

{
  "hooks": {
    "UserPromptSubmit": {
      "command": "afplay /path/to/start.mp3 &",
      "description": "Play sound when user submits prompt"
    },
    "Stop": {
      "command": "afplay /path/to/complete.mp3 &",
      "description": "Play sound when Copilot finishes"
    },
    "Notification": {
      "command": "afplay /path/to/question.mp3 &",
      "description": "Play different sound when Copilot needs input"
    }
  }
}

[axsaucedo]

+1

[tykeal]

I really want this so I can use https://github.com/PeonPing/peon-ping with copilot-cli! 😀

[ThePlenkov]

We need global hooks for agent sessions on Github too

[logar16]

I have a little GUI dashboard I made for tracking the sessions via hooks, but it's just for me. I don't want my team to have to have these in the repo if it's just for local tools. Global hooks would allow me to do my own thing (and not have to repeat myself).

[RajatGarga]

In their first version of documentation they allowed global hooks via ~/.claude/settings.json

I guess they are enshittifying copilot for some reason. Maybe global instructions, hooks etc will be just for enterprise customers.

I just got claude and copilot's config is not working with it so I was looking for a workaround and realized that MSFT in their divine judgement apparently don't even mention it anymore.

[nakashon]

Adding a concrete use case here: I'm working on adding Copilot CLI support to agent-of-empires (https://github.com/njbrake/agent-of-empires), a tool that tracks and manages AI agent sessions. AoE uses hooks to detect

agent status — userPromptSubmitted/preToolUse → running, sessionEnd → idle.
The per-project .github/hooks/hooks.json approach works for single-repo automation, but it's a blocker for session management tools like AoE that need hooks to fire regardless of which project directory is active. Claude Code solves this with ~/.claude/settings.json — a global hooks file that applies everywhere.

I verified hooks are working in Copilot CLI today (March 2026) and the event model is solid. The missing piece is just the global config path. Would make AoE integration clean and eliminate a whole class of special-casing.