[BUG] /hooks shows read-only [Plugin] PostToolUse entries with no visible source

Resolved 💬 3 comments Opened Feb 27, 2026 by Adamcf123 Closed Mar 3, 2026

Preflight Checklist

  • [x] I searched existing issues and found related reports, but not this exact behavior.
  • [x] This is a single bug report.
  • [x] I am using a recent Claude Code version.

What's Wrong?

/hooks shows read-only plugin hook entries such as:

  • [Plugin] Edit (1 hook)
  • [Plugin] Glob (1 hook)
  • [Plugin] Grep (1 hook)
  • [Plugin] Read (1 hook)
  • [Plugin] Write (1 hook)
  • [Plugin Hook] (read-only) Plugin Hooks - disable plugin to remove

But I cannot find any corresponding hook definitions in user/project/local settings or plugin hook JSON files.

The entries look like “ghost plugin hooks” because:

  1. They appear in the hooks UI as plugin-sourced and read-only.
  2. They are not traceable to any visible user-defined plugin hook config.
  3. The UI message says “disable plugin to remove,” but there is no clear removable source.

Expected Behavior

  • If hooks are internal/runtime callbacks, they should be labeled as internal (not plugin hooks).
  • If hooks are truly plugin hooks, the UI should clearly identify the exact plugin/source.
  • The message “disable plugin to remove” should only appear when that action is actually possible and unambiguous.

Actual Behavior

  • /hooks displays the read-only [Plugin] entries above.
  • Tool usage (e.g., Read/Grep/Glob/Edit/Write) shows PostToolUse callback activity.
  • No matching visible plugin hook definitions are found in settings/plugin hook files.

Steps to Reproduce

  1. Start Claude Code.
  2. Open /hooks.
  3. Navigate to PostToolUse matcher list.
  4. Observe read-only [Plugin] entries for common tools (Read/Grep/Glob/Edit/Write).
  5. Run one of those tools and observe PostToolUse callback hook activity.

Additional Diagnostics

  • User settings only contain normal explicit hooks (e.g., a Stop hook), not these PostToolUse plugin entries.
  • Installed/enabled plugin state does not clearly explain these exact entries.
  • Session hook progress indicates callback-style PostToolUse execution for those tools.

Claude Code Version

2.1.62

Platform

Linux (WSL2)

Operating System

Ubuntu on WSL2

Terminal/Shell

bash

Related Issue

Possibly related to: #21836
But this report focuses specifically on read-only [Plugin] PostToolUse entries that appear without a traceable visible plugin hook definition and with potentially misleading UI labeling.

View original on GitHub ↗

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