[FEATURE] add wildcard rule for permission prompt

Resolved 💬 3 comments Opened Mar 27, 2026 by natalikoifman-cpu Closed Mar 30, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

the permission prompt allows adding future permission for only the precise command being executed.

Proposed Solution

when the permission prompt appears, add a third option like "Yes, always allow py pytest *" that auto-generates a wildcard rule for the base command, so you don't have to manually edit settings.json every time.

Alternative Solutions

Doing it manually in settings.json as wildcard

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

  1. Claude tries to run python -m pytest tests/test_api_key_store.py tests/test_org_store.py tests/test_llm_router.py tests/test_webhook.py tests/test_v1_middleware.py --tb=no -q 2>&1
  2. asks for user permission and optionally put python -m pytest tests/test_api_key_store.py tests/test_org_store.py tests/test_llm_router.py tests/test_webhook.py tests/test_v1_middleware.py --tb=no -q 2>&1 in the allow list
  3. next time claude tries to run python -m pytest tests/test_api_key_store.py tests/test_org_store.py --tb=no -q 2>&1 (slightly different command, same base command)
  4. again asks for user permission for that specific command string
  5. on and on
  6. after a while the "allow list" becomes very long
  7. the user becomes very frustrated (me!)

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗