marketing: FRE-199 CTO review fixes — B1 precedence order, B2 false git-push example dropped, N1 hooks-guide attribution
B1 (agent-waiting-on-permission): body said 'allow / ask / deny' — inverted vs the permissions doc's deny → ask → allow. Fixed; fact-check row 3 was already correct and now matches the body. B2 (agent-run-without-asking): dropped the 'Bash(git commit *) allowed with Bash(git push *) denied is a policy the agent cannot talk its way around' example — the docs' own 'What a Bash rule doesn't match' table names Bash(git push *) as not stopping git -C . push origin main and friends. Sentence narrowed to the precedence claim, with a pointer to step 4's caveat. N1 (agent-done-signal): the osascript desktop-notification example is in the hooks guide (code.claude.com/docs/en/hooks-guide), not the hooks reference. Body and fact-check row 4 fixed. Pair-1 citations standardised from docs.anthropic.com to code.claude.com per the review's optional note. Each page's status blockquote records the revision.
This commit is contained in:
@@ -5,6 +5,10 @@
|
||||
> places it on nook.freno.me from `approved/`.
|
||||
> This page never names a product of ours and never names a competitor.
|
||||
> Internal target: second page of the FRE-199 pair, Fri 2026-11-07.
|
||||
> CTO review 2026-11-05: changes requested and applied — rule precedence
|
||||
> corrected to deny / ask / allow (body previously read allow / ask / deny,
|
||||
> contradicting the fact-check table and the source); pair-1 citations
|
||||
> standardised to code.claude.com.
|
||||
|
||||
Because it tried to do something its permission settings don't allow, and the
|
||||
default is to wait — indefinitely and quietly — for you. The prompt is not the
|
||||
@@ -16,7 +20,7 @@ not to approve faster, it's to make the prompts rare and the waiting visible.
|
||||
Claude Code's permission system decides, per tool call, whether to run, refuse,
|
||||
or stop and ask. In its `default` mode, it prompts for permission on the first
|
||||
use of each tool. Modes are set with `defaultMode` in the settings files, and a
|
||||
session's rules come from allow / ask / deny lists evaluated in that order —
|
||||
session's rules come from deny / ask / allow lists evaluated in that order —
|
||||
the first match wins.
|
||||
|
||||
You can see the whole rule set at any time with `/permissions`, which lists
|
||||
@@ -67,13 +71,13 @@ Code's behaviour come from its own documentation, re-read 2026-11-05.
|
||||
|
||||
| # | Claim in the page | Source |
|
||||
|---|---|---|
|
||||
| 1 | In `default` mode Claude Code "prompts for permission on first use of each tool" | Claude Code permissions doc — https://docs.anthropic.com/en/docs/claude-code/permissions (Permission modes table) |
|
||||
| 1 | In `default` mode Claude Code "prompts for permission on first use of each tool" | Claude Code permissions doc — https://code.claude.com/docs/en/permissions (Permission modes table) |
|
||||
| 2 | `defaultMode` in settings files sets the default mode for new sessions | same permissions doc (Permission modes section) |
|
||||
| 3 | Rules are evaluated deny → ask → allow, first match wins | same permissions doc (Permission rule syntax) |
|
||||
| 4 | `/permissions` lists all permission rules and the settings.json each comes from | same permissions doc (Manage permissions) |
|
||||
| 5 | `Bash(npm run build)` matches the exact command; `Bash(git log *)` wildcard form | same permissions doc (Use specifiers for fine-grained control) |
|
||||
| 6 | `acceptEdits` "automatically accepts file edits and common filesystem commands such as mkdir, touch, mv, cp for paths in the working directory" | same permissions doc (Permission modes table) |
|
||||
| 7 | A `Notification` hook fires when Claude Code sends a notification; permission prompts carry `notification_type: "permission_prompt"` and a message like "Claude needs your permission" | Claude Code hooks reference — https://docs.anthropic.com/en/docs/claude-code/hooks (Notification event) |
|
||||
| 7 | A `Notification` hook fires when Claude Code sends a notification; permission prompts carry `notification_type: "permission_prompt"` and a message like "Claude needs your permission" | Claude Code hooks reference — https://code.claude.com/docs/en/hooks (Notification event) |
|
||||
| 8 | Undo-split practice ("free hand on what git can undo, confirmation on what it can't") | r/ClaudeCode 1xkoz06 (2026-10-31, u/tomm3hshipp thread), commenter's described practice, logged in `drafts/listening.md` Scan 3 addendum. Described as one operator's approach, not a rule. |
|
||||
| 9 | The 55-minutes-lost framing | r/ClaudeAI 1xhbc71 (2026-10-28): "coming back an hour later to find it's been sitting on a permission prompt for 55 minutes". Used as the problem's shape, not quoted as a person. |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user