stop-hook-brainstorming-infinite-loop-pattern

When a brainstorming session is mid-flow (step 4 of 9, awaiting user section approval) and the user goes idle, the stop hook fires repeatedly on every idle timeout — each time blocking the stop and returning the agent to a waiting state. This creates an infinite loop: hook blocks → agent sends holding message → user doesn’t respond → hook fires again. The stop hook’s ‘structural incompleteness’ logic overrides the ‘pure planning session = APPROVE’ criterion, causing the cycle to repeat indefinitely until the user returns.

Related

• stop-hook-infinite-loop-when-brainstorming-awaits-user-input
• stop-hook-brainstorm-workflow-infinite-block-pattern
• stop-hook-blocks-mid-stream-brainstorming-sessions
• stop-hook-brainstorming-skill-deadlock-loop
• stop-hook-infinite-loop-on-pure-planning-sessions
• subagent-grep-scratch-files-accumulate-in-tmp-without-cleanu
• stop-hook-false-positive-during-active-waiting-state
• stop-hook-needs-agent-stop-intent-guard
• stop-hook-false-positive-loop-on-waiting-state
• stop-hook-false-positive-during-agent-waiting-state
• stop-hook-false-positive-loop-on-agent-waiting-state
• stop-hook-false-positive-on-minimal-agent-responses
• stop-hook-fires-on-waiting-state-not-just-session-end