claude-code - 💡(How to fix) Fix Bash tool calls not in allowlist executed without authorization prompt [1 comments, 2 participants]

TL;DR

Review and update the settings.json allowlist to ensure it correctly handles git commands and consider adding a catch-all rule to enforce authorization prompts for unknown commands.

Guidance

• Verify that the settings.json file is being read correctly by the application and that the allowlist rules are being applied as expected.
• Check for any typos or incorrect formatting in the allowlist rules that might be causing the authorization prompt to be skipped.
• Consider adding a broad allow rule for git commands (e.g. git(*)) to the allowlist, but be cautious of potential security implications.
• Test the authorization prompt with different Bash commands to ensure it is working as expected.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The issue may be related to how the allowlist rules are being interpreted or applied, and further investigation is needed to determine the root cause. The fact that the session was running a skill may be relevant, but without more information, it's unclear how this affects the authorization layer.

Recommendation

Apply a workaround by updating the settings.json allowlist to include specific rules for the git commands that are being executed without prompting, and consider adding a catch-all rule to enforce authorization prompts for unknown commands. This is recommended because it allows for a more targeted and secure approach to managing command authorization.