stop-hook-fires-on-agent-idle-waiting-state-false-positive
The Stop hook triggers repeatedly (~30+ times in one session) when the agent is in a mid-conversation waiting state (asked a clarifying question, awaiting user input) rather than on actual agent-stop events. The hook_event_name is ‘Stop’ but no stop() call or agent-initiated termination has occurred — it is a false-positive triggered by the idle/paused state during brainstorming flows. Root cause: the hook does not distinguish between ‘agent yielded control to user’ and ‘agent completed and stopped’.
Related
- stop-hook-false-positive-during-active-waiting-state
- stop-hook-false-positive-during-waiting-state
- stop-hook-fires-on-every-turn-not-just-agent-stop
- stop-hook-false-positive-during-agent-waiting-state
- stop-hook-false-positive-loop-on-waiting-state
- stop-hook-fires-on-agent-waiting-state-not-only-stop
- stop-hook-fires-false-positives-on-agent-waiting-state
- stop-hook-needs-agent-stop-intent-detection-not-just-event-n
- stop-hook-false-positive-during-agent-wait-states
- stop-hook-fires-on-idle-wait-state-false-positive-loop
- stop-hook-fires-on-user-wait-not-just-agent-stop
- stop-hook-fires-repeatedly-on-passive-agent-waiting-state
- stop-hook-fires-on-every-assistant-turn-not-just-stop
- stop-hook-fires-on-agent-idle-state-not-just-termination