claude-code - 💡(How to fix) Fix Allow trusting writes to ~/.claude/scheduled-tasks/ via permissions config [1 comments, 2 participants]

TL;DR

Modify the permission system to exempt ~/.claude/scheduled-tasks/** from hardcoded protection, allowing it to be covered by the normal permission rules.

Guidance

• Review the current implementation of the permission system, specifically the hardcoded protection for ~/.claude/, to understand how it can be modified to exempt certain subdirectories.
• Consider adding a new setting to allow users to opt specific subdirectories into the normal permission system, providing more flexibility and control.
• Evaluate the potential security implications of exempting ~/.claude/scheduled-tasks/** from hardcoded protection, ensuring that sensitive config files remain protected.
• Investigate the possibility of using explicit path globs, such as Write(~/.claude/scheduled-tasks/**), to grant permissions for scheduled tasks while maintaining protection for other config files.

Example

No code example is provided, as the issue does not contain sufficient technical details to generate a specific code snippet.

Notes

The proposed solution requires careful consideration of the security implications and potential trade-offs between flexibility and protection. The hardcoded protection for ~/.claude/ is likely in place to prevent unauthorized access to sensitive config files.

Recommendation

Apply a workaround by modifying the permission system to exempt ~/.claude/scheduled-tasks/** from hardcoded protection, allowing it to be covered by the normal permission rules, as this approach balances the need for flexibility with the requirement to protect sensitive config files.