stop-hook-false-positive-on-waiting-state
The Stop hook fires repeatedly when the agent outputs minimal responses (e.g., ’.’) while waiting for user input, not only when the agent actually terminates. This causes a flood of hook feedback messages in the conversation thread. The hook’s condition ‘Before allowing the agent to stop’ is evaluated against idle/waiting states, not just genuine stop() calls. Fix: add detection in the hook script to distinguish agent-initiated stop events from passive waiting states before evaluating completion gates.
Related
- stop-hook-false-positive-during-waiting-state
- stop-hook-false-positive-during-active-waiting-state
- stop-hook-false-positive-loop-on-waiting-state
- stop-hook-false-positive-during-agent-waiting-state
- stop-hook-false-positive-loop-on-agent-waiting-state
- stop-hook-fires-on-every-agent-turn-not-just-session-end
- stop-hook-false-positive-on-minimal-agent-responses
- stop-hook-needs-agent-stop-intent-detection-not-response-len
- stop-hook-fires-on-every-turn-not-just-agent-stop
- stop-hook-feedback-loop-bloats-context-window
- stop-hook-fires-on-idle-wait-state-false-positive-loop
- stop-hook-fires-on-agent-waiting-state-not-just-stop
- stop-hook-fires-on-idle-agent-not-just-stop-calls
- stop-hook-fires-on-idle-wait-not-just-agent-stop