anthropics / anthropics/claude-code
[DOCS] Clarify whether Recently denied approval is one-time or persistent
- Dominant language
- Python
- Stars
- 145k
- Forks
- 23.1k
- PR merge metrics
- PR metrics pending
Description
### Documentation Type
Missing documentation (feature not documented)
### Documentation Location
https://code.claude.com/docs/en/auto-mode-config
### Section/Topic
Review denials — /permissions > Auto mode > Recently denied
### Current Documentation
In Claude Code CLI 2.1.274, I could not determine from the “Review denials” documentation whether approving an action in /permissions > Auto mode > Recently denied grants one-time permission or creates a persistent permission rule.
### What's Wrong or Missing?
Please clarify:
1. Does pressing Enter to approve a recently denied action authorize only that execution, or save a persistent rule?
2. If a rule is saved, where is it stored and how narrowly does it match future commands?
3. How can users inspect the full command and approval scope before confirming?
4. How can users explicitly grant one-time approval?
The interface should clearly distinguish one-time approval from persistent permission before confirmation.
Observed denial labels: “Security Weaken” and “Auto-Mode Bypass”. I have not confirmed whether approval creates a persistent rule; this report requests clarification.
### Suggested Improvement
Document the exact scope of approval in Recently denied: whether it authorizes one execution or saves a persistent rule. Explain how to inspect the full action before approval and how to review or revoke any saved rule. Include an example of granting one-time approval while keeping existing protections enabled.
### Impact
High - Prevents users from using a feature
### Additional Context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Open the auto-mode-config documentation at the linked URL and read the Review denials section for /permissions > Auto mode > Recently denied. Verify the approval behavior and scope from the documented interface or available product behavior, then update the section to distinguish one-time approval, persistent rules, inspection, storage, and revocation; done means each requested question is answered clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100