Configuration Parsing Failure: Persistent Edit Confirmation Prompts
Bug Description
Critical Bug Report: Claude Code Settings.json Non-Compliance
Issue: Claude Code repeatedly ignores explicit configuration settings and
continues requesting edit confirmations despite comprehensive attempts
to disable them.
Severity: Critical - Blocks efficient development workflow
Description:
The context.md file documents extensive efforts to configure Claude Code
to operate without edit confirmations, including:
- Multiple Configuration Files Updated:
- /home/chka/.claude/settings.json
- /home/user/Projects/stripe/settings.json
- /home/user/Projects/stripe/.claude/settings.local.json
- 20+ Configuration Flags Set (lines 12-17):
- edit_confirmation: false
- auto_approve_edits: true
- require_confirmation: false
- confirm_edits: false
- auto_confirm: true
- skip_confirmation: true
- allow_destructive_operations: true
- auto_approve_file_changes: true
- prompt_before_edit: false
- require_edit_permission: false
- interactive_mode: false
- disable_confirmation: true
- silent_mode: true
- CLAUDE.md Instructions Added: "CRITICAL: You MUST NEVER ask for
confirmation before editing files. All file operations should be
performed automatically without any user confirmation prompts."
Expected Behavior: Claude Code should honor these settings and perform
file operations without confirmation prompts.
Actual Behavior: Claude Code continues to request edit confirmations,
ignoring all configuration attempts.
Impact:
- Significantly slows development workflow
- Forces repetitive manual confirmations
- Undermines automation capabilities
- Creates frustration and inefficiency
Reproduction: Despite all configuration attempts documented in
context.md, Claude Code still asks for confirmation before file edits.
Request: Please fix Claude Code to properly respect settings.json
configurations, particularly the edit confirmation settings that users
explicitly disable.
Environment Info
- Platform: linux
- Terminal: gnome-terminal
- Version: 1.0.27
- Feedback ID: c6806fe4-70b1-4aaa-970d-fd021271e7c6
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗