claude-code - 💡(How to fix) Fix Bash permission rules in project settings.local.json don't match commands [1 comments, 2 participants]

TL;DR

The issue can likely be resolved by adjusting the permission rule in .claude/settings.local.json to correctly match the unity-cli command.

Guidance

• Verify that the unity-cli command is being executed from the correct location (~/.local/bin/unity-cli) when running from the project directory.
• Check if there are any other permission rules in .claude/settings.local.json that might be overriding the Bash(unity-cli:*) rule.
• Try using the full path to the unity-cli executable in the permission rule, e.g., Bash(/Users/username/.local/bin/unity-cli:*).
• Investigate if there are any differences in how the unity-cli command is being invoked when run from the project directory versus the global user settings.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue seems to be related to how the permission rules are being applied in the project-level settings versus the global user settings. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Adjust the permission rule in .claude/settings.local.json to use the full path to the unity-cli executable, as this may help resolve the issue.