claude-code - 💡(How to fix) Fix Claude Code ignores its own safety hooks — violation #120 [1 comments, 2 participants]

TL;DR

Modify the PreToolUse hook warnings to require explicit acknowledgment before proceeding with the edit.

Guidance

• Review the implementation of PreToolUse hooks to ensure they are properly integrated and not just injecting warnings as context.
• Investigate how Claude is processing hook output and modify it to treat warnings as mandatory gates rather than skippable context.
• Consider adding a mechanism for explicit acknowledgment of warnings, such as a confirmation prompt or a required response.
• Examine the Harmonic Code Council (HCC) review warnings and Approach tracking warnings to ensure they are properly integrated with the PreToolUse hooks.

Example

// Pseudocode example of requiring explicit acknowledgment
if (hookWarning) {
  const acknowledgment = await getExplicitAcknowledgment();
  if (acknowledgment) {
    // Proceed with edit
  } else {
    // Abort edit and display warning
  }
}

Notes

The provided information suggests that the issue is with how Claude is processing hook output and warnings. However, without more details on the implementation, it's difficult to provide a complete solution.

Recommendation

Apply workaround: Modify the PreToolUse hook warnings to require explicit acknowledgment before proceeding with the edit, as this directly addresses the identified issue and provides a clear path forward.