Feature request: Hook for when permission prompt is answered

Resolved 💬 3 comments Opened Jan 21, 2026 by edvintb Closed Jan 24, 2026

Description

Currently there is no hook that fires when a user answers a permission prompt (grants or denies permission). This makes it difficult to implement proper notification dismissal workflows.

Use case

When using Notification hooks to alert users about permission prompts (e.g., via desktop notifications), the ideal time to dismiss the notification is when the user responds to the permission prompt - not when they type their next message.

Current workaround

Using UserPromptSubmit or PreToolUse hooks to dismiss notifications, but these fire at the wrong time:

  • UserPromptSubmit fires when the user types a new prompt, not when they answer a permission
  • PreToolUse fires before tool execution, which may not align with permission responses

Suggested solutions

Option A: New hook event

A new hook event, e.g., PermissionPromptResponse, that fires immediately when the user answers a permission prompt:

{
  "hooks": {
    "PermissionPromptResponse": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "~/bin-personal/claude-notify-dismiss.sh"
          }
        ]
      }
    ]
  }
}

Option B: Extend existing Notification hook

Add a new matcher to the existing Notification hook, e.g., permission_response or permission_answered:

{
  "hooks": {
    "Notification": [
      {
        "matcher": "permission_response",
        "hooks": [
          {
            "type": "command",
            "command": "~/bin-personal/claude-notify-dismiss.sh"
          }
        ]
      }
    ]
  }
}

This option might be simpler since it reuses the existing hook infrastructure.

Payload

Ideally the hook payload would include:

  • Whether permission was granted or denied
  • Which tool/action the permission was for

This would allow notification systems to dismiss alerts immediately when the user interacts with the permission prompt, providing a cleaner UX.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗