claude-code - 💡(How to fix) Fix Bash tool executed `brew install` without prompting user for approval [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48770Fetched 2026-04-16 06:51:27
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×5commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

Bug

A Bash(brew install kubeconform) command executed successfully without prompting the user for approval, despite no matching allow rule in the user's permission configuration.

Expected behavior

The permission system should have prompted the user before executing brew install, since no allowlist pattern matches it.

Actual behavior

The command ran to completion and installed the package without any user prompt.

Relevant config

  • User settings (~/.claude/settings.json): only allows gh pr view/diff/checks/list/status
  • Project settings (.claude/settings.json): only allows scoped pnpm --filter, git log/diff/status
  • Project local settings (.claude/settings.local.json): only allows WebFetch for specific domains
  • No Bash(brew *) or Bash(*) wildcard present in any config

Environment

  • Claude Code running inside VSCode extension (v2.1.109)
  • Helm v4.0.0
  • macOS (Darwin 25.3.0)

extent analysis

TL;DR

The permission system may not be correctly configured or prioritizing rules, allowing the Bash(brew install) command to execute without user approval.

Guidance

  • Review the permission configuration files (~/.claude/settings.json, .claude/settings.json, and .claude/settings.local.json) to ensure that there are no implicit allow rules or missing deny rules that could be bypassing the expected behavior.
  • Check the documentation for the Claude Code VSCode extension (v2.1.109) to understand how it handles permission configurations and if there are any known issues or limitations.
  • Verify that the Bash(brew install) command is not being executed through a different path or alias that might not be covered by the current permission rules.
  • Consider adding an explicit deny rule for Bash(brew *) to test if the permission system is correctly applying the rules.

Example

No code snippet is provided as the issue is related to configuration and permission rules.

Notes

The issue might be related to the specific version of the Claude Code VSCode extension or the Helm version, but without further information, it's difficult to determine the root cause.

Recommendation

Apply a workaround by adding an explicit deny rule for Bash(brew *) to the permission configuration to ensure that the command is properly restricted until the root cause is identified and fixed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The permission system should have prompted the user before executing brew install, since no allowlist pattern matches it.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING