story-kit: create 219_story_add_always_allow_option_to_web_ui_permission_dialog
This commit is contained in:
@@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
name: "Add \"Always Allow\" option to web UI permission dialog"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Story 219: Add "Always Allow" option to web UI permission dialog
|
||||||
|
|
||||||
|
## User Story
|
||||||
|
|
||||||
|
As a user interacting with agents via the web UI, I want an "Always Allow" option in the permission dialog, so that I don't have to repeatedly approve the same tool operations.
|
||||||
|
|
||||||
|
## Acceptance Criteria
|
||||||
|
|
||||||
|
- [ ] Permission dialog shows three buttons: Deny, Approve, Always Allow
|
||||||
|
- [ ] Clicking Always Allow writes the permission rule to .claude/settings.json
|
||||||
|
- [ ] After Always Allow, Claude Code's built-in permission system handles future checks without calling the prompt tool
|
||||||
|
- [ ] Edit and Write rules use the tool name (e.g. Edit, Write)
|
||||||
|
- [ ] Bash rules use the command prefix pattern (e.g. Bash(git *))
|
||||||
|
- [ ] MCP tool rules use the tool name pattern (e.g. mcp__story-kit__create_story)
|
||||||
|
- [ ] Existing rules in settings.json are not duplicated
|
||||||
|
|
||||||
|
## Out of Scope
|
||||||
|
|
||||||
|
- TBD
|
||||||
Reference in New Issue
Block a user