claude-code - 💡(How to fix) Fix [BUG] "Yes, and always allow" never persists for edits inside `.claude/` directories [1 comments, 2 participants]

Error Messages/Logs

TL;DR

The issue can be fixed by modifying the code to correctly handle the persistence of "always allow" permissions for edits within the .claude/ directory.

Guidance

• Investigate the code responsible for writing permission rules to ~/.claude/settings.json or project .claude/settings.local.json to ensure it correctly handles .claude/ paths.
• Verify that the UI's "always allow" option is properly connected to the underlying permission system, and that the system is not filtering out .claude/ paths as a safety guard.
• Check the differences in how "always allow" permissions are handled for paths outside of .claude/ to identify potential inconsistencies in the code.
• Test the permission persistence with different file paths and patterns within the .claude/ directory to ensure the issue is not specific to a particular file or location.

Example

No specific code snippet can be provided without more information about the internal workings of Claude Code, but the investigation should focus on the functions or methods responsible for writing permission rules and handling the "always allow" option.

Notes

The issue may be related to a safety guard or filtering mechanism that prevents certain paths from being written to the permission rules, but without more information about the codebase, it's difficult to provide a more specific solution.

Recommendation

Apply a workaround by manually adding the necessary Edit rule to ~/.claude/settings.json or project .claude/settings.local.json until the underlying issue can be resolved, as the automatic persistence of "always allow" permissions for edits within the .claude/ directory appears to be faulty.