futpib / claudex / 22678860615 / 3

64%

master: 64%

push

github

Use permissionDecision ask instead of exit-code-2 for write ops rule

Switch ban-write-operations from hard-blocking (exit 2) to forcing a
user approval prompt via hookSpecificOutput permissionDecision "ask".
This ensures the user sees a confirmation dialog even when they have
pre-approved the tool (e.g. Bash(curl *)).

In bypassPermissions mode, fall back to exit-code-2 since "ask" would
be auto-approved and defeat the purpose. Add RuleAsk result type as a
general capability any rule can use. Parse permission_mode from hook
input to support mode-aware decisions.

Co-authored-by: Claude <noreply@anthropic.com>

957 of 1237 branches covered (77.36%)

Branch coverage included in aggregate %.

4307 of 6795 relevant lines covered (63.38%)

70.17 hits per line