stop-hook-brainstorming-workflow-infinite-loop
The stop hook’s ‘structural incompleteness’ check for active brainstorming workflows conflicts with the pure-planning APPROVE criterion, creating an infinite blocking loop when the agent is mid-brainstorming and awaiting user input. The hook correctly identifies incomplete workflow state but cannot distinguish between ‘user is away’ and ‘session is truly done.’ This session generated 30+ identical block cycles with no resolution. The stop hook condition needs a timeout or idle-user-absent exemption to prevent runaway context consumption.
Related
- stop-hook-loop-on-mid-workflow-user-silence
- stop-hook-infinite-loop-on-pure-planning-sessions
- stop-hook-brainstorm-workflow-infinite-block-when-user-away
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- stop-hook-blocks-mid-stream-brainstorming-sessions
- stop-hook-deadlock-on-awaiting-user-input-sessions
- subagent-grep-scratch-files-accumulate-in-tmp-without-cleanu
- stop-hook-false-positive-loop-on-waiting-state