stop-hook-brainstorm-workflow-infinite-block-when-user-away
When the stop hook evaluates session completeness against an active brainstorming workflow awaiting section-by-section user approval, it will block every stop attempt indefinitely if the user steps away mid-flow. The hook correctly identifies structural incompleteness but has no timeout or idle-detection — agent ends up in a loop of ‘blocked → respond → blocked’ generating dozens of identical holding messages. Consider adding idle-time threshold (e.g., 10+ blocks without user response) to allow graceful session closure.
Related
- stop-hook-brainstorm-workflow-infinite-block-pattern
- stop-hook-infinite-loop-when-brainstorming-awaits-user-input
- stop-hook-infinite-loop-on-pure-planning-sessions
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- stop-hook-brainstorming-skill-deadlock-loop
- brainstorming-stop-hook-infinite-loop-when-user-goes-silent
- stop-hook-blocks-mid-brainstorm-workflow-correctly
- stop-hook-infinite-loop-during-brainstorming-mid-session
- stop-hook-blocks-mid-stream-brainstorming-sessions
- stop-hook-brainstorming-workflow-infinite-loop