chore(claude): allow scheduling and notification tools without prompting - #344
Merged
Merged
Conversation
Auto mode routes CronCreate and RemoteTrigger through the classifier unconditionally — both are members of the always-classify tool set, so the "would this be allowed in acceptEdits mode?" fast path is skipped and every call surfaces a prompt. ScheduleWakeup is in the same set. The result was a steady stream of approve/deny prompts for the routine CI-check-in machinery (arm a cron, arm a routine, ping when done), which blocks unattended workflows from progressing. A whole-tool allow rule resolves before the classifier runs, and neither tool declares ignoresWholeToolAllowRule, so bare tool-name entries clear the prompts without weakening anything else: none of these six execute shell, edit files, or touch the network beyond the claude.ai routines API. Added to both scopes deliberately: - exact_dot_claude/modify_settings.json — local and Remote Control sessions - .claude/settings.json — Claude Code web/remote, which cannot read ~/.claude Monitor is intentionally left out: it runs arbitrary shell, so it does not belong in the same "benign and contained" bucket. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017AF6S4A2q5ha5Yhk8duyMp
Contributor
|
| Status | Count |
|---|---|
| 🔍 Total | 170 |
| ✅ Successful | 160 |
| ⏳ Timeouts | 0 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 9 |
| ❓ Unknown | 0 |
| 🚫 Errors | 1 |
Errors per input
Errors in exact_dot_claude/docs/prds/daily-catchup.PRD.md
- [404] https://docs.anthropic.com/claude-code/commands | Failed: Network error: Not Found
Full Github Actions output
Please fix the broken links before merging.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds six bare tool-name entries to
permissions.allowin both the global chezmoi overlay and this repo's committed project settings:CronCreate·CronDelete·CronList·PushNotification·RemoteTrigger·ScheduleWakeupWhy
Under
defaultMode: "auto",CronCreate,RemoteTrigger, andScheduleWakeupare members of the CLI's always-classify tool set. That set is checked before the "would this be allowed in acceptEdits mode?" fast path, so the fast path never runs for them and every call goes to the auto-mode classifier — producing a constant stream of approve/deny prompts for routine PR-CI check-in machinery (arm a cron, arm a claude.ai routine, ping when it finishes). Unattended workflows stall on them.A whole-tool allow rule resolves before the classifier, and none of these tools declares
ignoresWholeToolAllowRule, so the bare-name entries clear the prompts cleanly. None of the six executes shell, edits files, or reaches the network beyond the claude.ai routines API.Two scopes on purpose
exact_dot_claude/modify_settings.json.claude/settings.json~/.claudePer
rules/claude-plugins-freshness.md, the committed project settings are the only path that reaches web sessions. Other repos used from web need the same six entries added to their own.claude/settings.json.Not included
Monitor— it runs arbitrary shell, so it does not belong in the same "benign and contained" bucket.Verification
chezmoi diff ~/.claude/settings.jsonshowed only the intended addition (no runtime drift clobbered), applied, then re-diffed clean.jqconfirms the six entries are live in~/.claude/settings.json.check json, gitleaks, conventional commit).🤖 Generated with Claude Code
https://claude.ai/code/session_017AF6S4A2q5ha5Yhk8duyMp