stop-hook-infinite-loop-on-pure-planning-sessions
The Stop hook’s ‘structural incompleteness’ logic for brainstorming workflows creates an infinite blocking loop when the user goes inactive mid-session without providing section approval. The hook correctly identifies the workflow is mid-stream but then fires 30+ times in succession, burning context and adding zero value. The fix: add a guard — if no file modifications occurred AND the block reason is ‘awaiting user input’ (not ‘agent has incomplete work’), APPROVE the stop after 3 consecutive blocks.
Related
- stop-hook-loop-on-mid-workflow-user-silence
- stop-hook-brainstorming-skill-deadlock-loop
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- stop-hook-infinite-loop-when-brainstorming-awaits-user-input
- stop-hook-brainstorm-workflow-infinite-block-when-user-away
- brainstorming-stop-hook-infinite-loop-when-user-goes-silent
- stop-hook-blocks-mid-brainstorm-workflow-correctly
- stop-hook-infinite-loop-during-brainstorming-await
- stop-hook-brainstorming-workflow-infinite-loop
- stop-hook-blocks-mid-brainstorming-session-by-design
- stop-hook-blocks-pure-planning-sessions-pathological-loop
- stop-hook-deadlock-on-awaiting-user-input-sessions
- stop-hook-brainstorming-infinite-loop-pattern
setup-curator-guard-stays-advisory-during-pre-approved-batch(archived)- parallel-subagent-temp-artifacts-require-explicit-cleanup
- documentation-cascade-must-not-defer-past-checkpoint