stop-hook-fires-false-positives-during-waiting-states
The Stop hook fires repeatedly when the agent is mid-conversation paused awaiting user input, not just when the agent actually initiates session termination. This creates a tight loop of hook evaluations during active brainstorming sessions. The hook condition logic needs to detect whether the agent actually called stop() versus being in an idle waiting state between turns.
Related
- stop-hook-false-positive-during-agent-wait-states
- stop-hook-fires-on-agent-wait-state-not-just-stop
- stop-hook-false-positive-during-waiting-state
- stop-hook-needs-agent-stop-intent-guard
- stop-hook-false-positive-loop-on-waiting-state
- stop-hook-false-positive-during-active-wait-state
- stop-hook-fires-on-agent-idle-state-not-just-termination