Context
The spec_stop_guard.py hook prevents Claude from stopping during /spec workflows. The only escape is a 60s double-tap (press Escape twice within 60 seconds), which is undiscoverable and impractical.
v7.2.1 upstream makes the guard even more aggressive ("Your VERY NEXT action must be a tool call"). Adopted in fork migration, but this increases the need for a reliable emergency stop.
Problem
When the user genuinely needs Claude to stop (derailing, wrong approach, wants to discuss), there's no clean way to do it. The double-tap mechanism is:
- Not documented in any user-facing place
- Requires knowing the 60s window
- Easy to miss the window
Desired Behavior
A clear, single-action emergency stop — e.g.:
- A specific keyword/phrase that bypasses the guard ("STOP", "/stop", "/abort")
- A hook that detects repeated Escape presses (not time-gated)
- A keybinding that sends a signal the hook recognizes
Related
Context
The spec_stop_guard.py hook prevents Claude from stopping during /spec workflows. The only escape is a 60s double-tap (press Escape twice within 60 seconds), which is undiscoverable and impractical.
v7.2.1 upstream makes the guard even more aggressive ("Your VERY NEXT action must be a tool call"). Adopted in fork migration, but this increases the need for a reliable emergency stop.
Problem
When the user genuinely needs Claude to stop (derailing, wrong approach, wants to discuss), there's no clean way to do it. The double-tap mechanism is:
Desired Behavior
A clear, single-action emergency stop — e.g.:
Related
spec_stop_guard.pychange that adds "VERY NEXT action must be a tool call"