Rank, 14 days: 139 on the Claude Code sheet
3 people reported
All time, since Oct 21, including 1 thumbs-up on GitHub.
Hook-skipped notices sent to model
“its classic.Stop hook was skipped. "cc-plugin-sec-default" runs first and sent the event on past it.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/20351/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Hook-skipped notices from cc-plugin-sec-default are queued to the model. Each notice is written as a transcript row and enqueued as a queue-operation, so the model receives it as a message and sometimes answers it.
Is this your bug?
File my report- Where
- Mods hook notices
- Error text
its classic.Stop hook was skipped. "cc-plugin-sec-default" runs first and sent the event on past it.- Versions
- 2.1.306 to 2.1.311
- Platforms
- macOS
- How bad
- Breaks a normal workflow.
Not quite your bug?
Original reports2, newest first
- Mods: "hook was skipped" notices are fed to the model in interactive and -p sessions too, not only background ones (contrary to the $.ui.log doc)#105311
- Background sessions: cc-plugin-sec-default's "hook was skipped" notices are queued to the model, and a skipped classic.Stop loses background_tasks#103962