stop-hook-deadlock-on-awaiting-user-input-sessions
The session-stop hook that validates brainstorming workflow completeness creates an infinite deadlock when the session is blocked waiting for user input — the hook correctly detects structural incompleteness but cannot distinguish between ‘agent hasn’t done work’ vs ‘agent is waiting for human’. This caused 30+ blocked stop attempts in a single session. Fix: the stop hook should detect when the agent’s last message is an explicit user-input await and APPROVE the stop rather than blocking it.
Related
- stop-hook-blocks-on-brainstorming-mid-flow
- stop-hook-brainstorming-workflow-infinite-loop
- stop-hook-infinite-loop-when-brainstorming-awaits-user-input
- stop-hook-infinite-loop-on-pure-planning-sessions
- brainstorming-stop-hook-infinite-loop-when-user-goes-silent
- stop-hook-must-guard-against-non-termination-stop-events
- stop-hook-fires-on-every-agent-turn-not-just-session-end
- stop-hook-fires-on-agent-wait-state-not-just-stop