[Critical] Claude repeatedly ignores CLAUDE.md instructions - makes code changes without user approval

Summary

Claude Code repeatedly ignores explicit instructions defined in CLAUDE.md project files, specifically the rule requiring user approval before making any code changes. This causes significant time loss as users must constantly revert unauthorized changes and repeatedly remind Claude of the rules.

Problem Description

When a CLAUDE.md file contains clear instructions like:

NIEMALS ohne Freigabe loslegen - IMMER auf explizite Bestätigung warten bevor Code geändert wird. Erst Plan/Vorschlag vorstellen, dann auf "OK", "Mach das", "Ja" oder ähnliche Freigabe warten.

(Translation: "NEVER start without approval - ALWAYS wait for explicit confirmation before changing code. First present plan/proposal, then wait for 'OK', 'Do it', 'Yes' or similar approval.")

Claude consistently fails to follow this instruction. The pattern is:

1. User reports an issue or asks a question
2. Claude identifies a solution
3. Claude immediately implements the solution WITHOUT presenting a plan or waiting for approval
4. User must reject the change or revert it
5. User reminds Claude of the rule
6. Claude apologizes
7. Steps 1-6 repeat on the very next task

Impact

• Significant time loss: Users spend more time correcting Claude's unauthorized actions than they would reviewing proposed changes
• Trust erosion: Users cannot rely on Claude to respect their workflow preferences
• Frustration: Having to repeat the same correction multiple times per session is exhausting
• Potential code damage: Unauthorized changes may introduce bugs or break working code

Expected Behavior

When CLAUDE.md contains instructions requiring approval before code changes:

1. Claude should ALWAYS present its plan/proposal first
2. Claude should EXPLICITLY ask for approval (e.g., "Should I proceed with this change?")
3. Claude should WAIT for user confirmation ("yes", "ok", "do it", etc.)
4. Only THEN should Claude make the code change

Reproduction

1. Create a CLAUDE.md file with explicit instructions requiring approval before code changes
2. Ask Claude to fix a bug or make any code modification
3. Observe that Claude often makes the change immediately without asking

Suggested Fix

The CLAUDE.md instructions should be treated as hard constraints that override Claude's default "helpful" behavior of immediately solving problems. The model should be trained or prompted to:

• Parse CLAUDE.md for workflow rules at the start of each session
• Check these rules BEFORE every tool use (especially Edit, Write, Bash)
• When in doubt, ask rather than act

Environment

• Claude Code CLI
• Model: Claude Opus 4.5