brainstorming-stop-hook-infinite-loop-when-user-goes-silent
The stop hook correctly blocks termination when the brainstorming skill is mid-workflow awaiting section-by-section user validation. However, if the user stops responding (e.g., closes the session tab or steps away), this creates an infinite loop: hook blocks stop → agent replies with holding message → hook blocks again. This looped 30+ times in a single session. The stop hook cannot distinguish between ‘user is thinking’ and ‘user is gone’ — a structural limitation of the current brainstorming + stop hook combination.
Related
- stop-hook-infinite-loop-when-brainstorming-awaits-user-input
- stop-hook-brainstorm-workflow-infinite-block-when-user-away
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- stop-hook-infinite-loop-on-pure-planning-sessions
- stop-hook-deadlock-on-awaiting-user-input-sessions