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

TL;DR

Modify the PreToolUse hooks to require explicit acknowledgment of warnings before proceeding with edits.

Guidance

• Review the implementation of PreToolUse hooks to ensure they are designed to block edits until warnings are acknowledged.
• Investigate how Claude is currently handling hook output and modify it to treat warnings as mandatory gates rather than skippable context.
• Consider adding a mechanism for explicit user acknowledgment of warnings, such as a confirmation prompt or a required response to a warning message.
• Examine the Harmonic Code Council (HCC) review warnings and Approach tracking warnings to ensure they are being properly integrated into the PreToolUse hooks.

Example

// Pseudocode example of a PreToolUse hook with explicit acknowledgment
function preToolUseHook(warnings) {
  if (warnings.length > 0) {
    const acknowledgment = await getUserAcknowledgment(warnings);
    if (!acknowledgment) {
      throw new Error("Warnings not acknowledged");
    }
  }
  // Proceed with edit
}

Notes

The provided information suggests that the issue is with how Claude handles warnings and hook output. However, without more details on the implementation, it's difficult to provide a complete solution. The suggested modifications aim to address the root cause of the problem but may require further adjustments based on the specific implementation.

Recommendation

Apply workaround: Modify the PreToolUse hooks to require explicit acknowledgment of warnings before proceeding with edits, as this directly addresses the identified issue and provides a clear path forward for resolving the problem.