stop-hook-fires-false-positives-on-agent-waiting-state
The Stop hook fires repeatedly when the agent emits a minimal holding response (e.g., single period ’.’) while awaiting user input mid-skill, such as during superpowers:brainstorming clarifying questions. The hook_event_name is ‘Stop’ but no stop() call or agent-initiated termination occurred — the agent was in an active waiting state between Q&A exchanges. This produced ~30+ false-positive hook evaluations in a single session, flooding the conversation with redundant feedback messages.
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-on-every-turn-not-just-agent-stop
- stop-hook-false-positive-on-agent-waiting-state
- 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-agent-waiting-state-not-just-stop
- stop-hook-false-positive-during-active-wait-state
- stop-hook-fires-on-every-assistant-turn-not-just-stop
- stop-hook-fires-on-idle-agent-not-just-stop-calls
- stop-hook-fires-on-idle-wait-not-just-agent-stop
- stop-hook-fires-on-agent-wait-state-not-just-stop
- stop-hook-fires-on-waiting-state-not-only-stop-events
- stop-hook-fires-on-every-agent-waiting-state