stop-hook-blocks-indefinitely-on-brainstorming-user-absence
The brainstorming skill mandates section-by-section user approval before advancing. When the user goes silent mid-session, the stop hook blocks termination indefinitely because the session is ‘structurally incomplete’ even though no files were modified. This creates an infinite blocking loop: agent can’t stop, user isn’t responding, hook fires on every stop attempt. Stop hook condition for pure planning sessions should distinguish ‘user absent’ from ‘work incomplete’ to allow graceful termination after N retries.
Related
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- brainstorm-stop-hook-deadlock-on-blocked-user-input
- brainstorming-skill-hardgate-overrides-stop-hook-pure-planni
- brainstorm-hard-gate-blocks-stop-hook-until-writing-plans-in
- 2026-04-04-oracle-001-self-architecture-analysis
- stop-hook-brainstorming-skill-deadlock-loop
- stop-hook-brainstorm-workflow-infinite-block-pattern
- stop-hook-loop-on-mid-workflow-user-silence
- stop-hook-infinite-loop-when-brainstorming-awaits-user-input
- stop-hook-blocks-pure-planning-sessions-infinite-loop
- stop-hook-blocks-pure-planning-sessions-in-brainstorm-loop
- stop-hook-infinite-loop-on-pure-planning-sessions
- 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-mid-session
- stop-hook-blocks-pure-planning-sessions-pathological-loop
- doc-sync-deferral-to-post-checkpoint-is-invalid
- documentation-cascade-must-not-defer-past-checkpoint