stop-hook-false-positive-during-agent-wait-states
The Stop hook fires repeatedly when the agent is in an idle/waiting state (paused mid-conversation awaiting user input), not just on actual agent-initiated stop events. This produces dozens of false-positive evaluations per session during normal brainstorming or Q&A flows. Root cause: the hook_event_name ‘Stop’ triggers on any session pause, not exclusively on agent stop() calls. Fix requires narrowing the hook trigger condition to detect actual agent termination intent vs. passive wait states.
Related
- stop-hook-fires-on-agent-idle-waiting-state-false-positive
- stop-hook-false-positive-during-waiting-state
- stop-hook-false-positive-during-active-waiting-state
- stop-hook-fires-false-positives-on-agent-waiting-state
- stop-hook-false-positive-loop-on-waiting-state
- stop-hook-fires-on-idle-wait-state-false-positive-loop
- stop-hook-fires-on-user-wait-not-just-agent-stop
- stop-hook-fires-false-positives-during-waiting-states
- stop-hook-false-positive-during-active-wait-state
- stop-hook-fires-on-agent-wait-state-not-just-stop
- stop-hook-fires-on-idle-wait-not-just-stop-calls
- stop-hook-fires-on-agent-idle-state-not-just-termination
- stop-hook-fires-on-every-assistant-turn-not-just-stop-calls
stop-hook-fires-on-idle-wait-states-not-just-stop- stop-hook-fires-on-waiting-state-not-only-stop-events