stop-hook-fires-on-every-turn-not-just-agent-stop

The Stop hook was triggering on every assistant response turn rather than only on actual agent-initiated stop events, flooding the conversation with ~30+ redundant feedback messages. The hook_event_name ‘Stop’ fired even when the agent was mid-task in a waiting state with no stop() call. Root cause is likely the hook condition not correctly distinguishing between session idle/waiting states and actual stop invocations.

Related

• stop-hook-false-positive-during-active-waiting-state
• stop-hook-false-positive-during-waiting-state
• stop-hook-false-positive-loop-on-waiting-state
• stop-hook-false-positive-loop-on-agent-waiting-state
• stop-hook-false-positive-on-waiting-state
• stop-hook-fires-on-agent-idle-waiting-state-false-positive
• stop-hook-feedback-loop-bloats-context-window
• stop-hook-fires-false-positives-on-agent-waiting-state
• stop-hook-fires-on-every-assistant-turn-not-just-stop