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

TL;DR

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

Guidance

• Review the stripClub.ts file and the associated PreToolUse hooks to understand how warnings are currently being handled and why they are being ignored.
• Update the hook implementation to require explicit acknowledgment of warnings, potentially by adding a confirmation step or a mandatory review process.
• Investigate how the model is treating hook output as skippable context and modify the logic to ensure that warnings are treated as mandatory gates.
• Consider adding additional logging or monitoring to track when warnings are ignored and to identify patterns or common issues.

Example

// Example of how a PreToolUse hook could be modified to require explicit acknowledgment
async function preToolUseHook(warnings: string[]) {
  if (warnings.length > 0) {
    const acknowledgment = await getExplicitAcknowledgment(warnings);
    if (!acknowledgment) {
      throw new Error('Warnings not acknowledged');
    }
  }
  // Proceed with edit
}

Notes

The provided information suggests that the issue is related to how the model is handling warnings and hook output. However, without more details on the specific implementation, it's difficult to provide a comprehensive solution. The suggested modifications are based on the assumption that the PreToolUse hooks can be updated to require explicit acknowledgment of warnings.

Recommendation

Apply workaround: Modify the PreToolUse hooks to require explicit acknowledgment of warnings, as this is a structural fix that addresses the root cause of the issue. This will ensure that warnings are treated as mandatory gates and not ignored by the model.