golem15/msd-core
4
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

fix(#925): context monitor echoes the invoking hook event name (#927)

Browse Source 
Read `data.hook_event_name` from the stdin payload and fall back to the
Gemini/non-Gemini heuristic only when the field is absent or blank.
Fixes Claude Code rejecting output with "expected Stop but got PostToolUse"
when the monitor is called by Stop, SubagentStop, or PreCompact hooks.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
(cherry picked from commit cf6d3b3be5)
This commit is contained in:
Tom Boucher
2026-06-09 08:42:16 -04:00
committed by github-actions[bot]
parent 7b6eae766a
commit 27af818312
3 changed files with 212 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.changeset/925-context-monitor-hook-event-name.md Normal file
View File

@@ -0,0 +1,5 @@
---
type: Fixed
pr: 926
---
**`gsd-context-monitor.js` now echoes the actual invoking hook event name** — instead of hardcoding `hookEventName: "PostToolUse"` (or `"AfterTool"` for Gemini), the hook reads `data.hook_event_name` from the stdin payload and falls back to the runtime heuristic only when the field is absent or blank; this fixes Claude Code rejecting hook output with `"expected Stop but got PostToolUse"` when the monitor is invoked by the Stop, SubagentStop, or PreCompact hooks registered in PR #821. (#925)