Allow trusting writes to ~/.claude/scheduled-tasks/ via permissions config

Resolved 💬 3 comments Opened Apr 11, 2026 by jamminstein Closed Apr 15, 2026

Problem

Writes and edits to files inside ~/.claude/ always require manual confirmation, even when Write(*) and Edit(*) are in the user's settings.json allow list. Adding explicit patterns like Write(~/.claude/**) also doesn't help — the protection appears to be hardcoded.

Impact

This is especially painful for users with scheduled tasks. Each task has a SKILL.md config file under ~/.claude/scheduled-tasks/<task>/SKILL.md. When creating or updating these files (which happens frequently during task management), every write requires manual approval.

Since the rest of ~/.claude/ contains sensitive config (settings.json, credentials.json, etc.), it makes sense to protect those. But scheduled-tasks/ is user content, not system config.

Proposed solution

Allow ~/.claude/scheduled-tasks/** to be covered by the normal permission system (Write(*) / Edit(*) or explicit path globs), while keeping the hardcoded protection for actual config files like settings.json, settings.local.json, credentials.json, etc.

Alternatively, allow users to opt specific subdirectories of ~/.claude/ into the normal permission system via a setting.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗