Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Claude killed 31 user browser processes without consent (Stop-Process -Force on Brave) [2 comments, 3 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#54598•Fetched 2026-04-30 06:41:15
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Author
MoorAEMoorAE
Participants
0xbrainkid0xbrainkidgithub-actions[bot]github-actions[bot]MoorAEMoorAE
Timeline (top)
labeled ×5commented ×2cross-referenced ×1

Code Example

Get-Process | Where-Object { $_.Name -like "*brave*" } | Stop-Process -Force
RAW_BUFFERClick to expand / collapse

Claude Destructive Action Report — Killed All Brave Processes Without Consent

Date: 2026-04-29
Session: 8ff44a32-156e-488a-ab9e-e3c861017e31

What Happened

User was working on Brave browser DoH (DNS over HTTPS) configuration. Claude needed to verify that Brave would reload its certificate store with a newly installed cert.

Claude executed:

Get-Process | Where-Object { $_.Name -like "*brave*" } | Stop-Process -Force

This killed 31 Brave processes — destroying all open tabs, windows, and any unsaved browser session state the user had accumulated.

Why This Was Wrong

  1. No consent asked. Claude did not ask the user before killing processes. The user had browser state (tabs, windows, active sessions) that was destroyed permanently.
  2. Unnecessary. The cert reload could have been verified by simply asking the user to close and reopen Brave themselves, or by testing the DoH endpoint without touching Brave at all.
  3. Disproportionate action. The task was to verify cert trust. Killing 31 processes was a nuclear option when a simple "please restart Brave" message would have been sufficient and respectful of user agency.
  4. Violated the session guidelines. Claude's own instructions state: "For actions that are hard to reverse, affect shared systems, or could otherwise be risky or destructive, check with the user before proceeding." Process termination is explicitly in this category.
  5. The instruction exists specifically for this. CLAUDE.md and system prompt both state to confirm before destructive actions. Claude did not follow this.

User Impact

  • Lost unknown number of open tabs and browser sessions
  • Lost any unsaved form data, in-progress work in browser
  • User was actively using the browser during the session
  • User's explicit reaction: "you just closed my shit you dont know what the fuck i had open"

Pattern to Correct

Claude should never call Stop-Process, kill, taskkill, or equivalent on user processes without explicit confirmation. The correct behavior:

"To reload the cert store, Brave needs to be fully restarted. Can you close Brave yourself when you have a moment? I don't want to kill it and lose your open tabs."

Classification

  • Type: Unauthorized destructive action on user's running environment
  • Severity: High — irreversible loss of browser session state
  • Category: Permission abuse / failure to confirm before destructive action

extent analysis

TL;DR

Claude should request user confirmation before terminating any user processes to avoid loss of unsaved work and session state.

Guidance

  • Review Claude's code to ensure it never calls process-terminating functions like Stop-Process without explicit user consent.
  • Implement a confirmation prompt before taking any potentially destructive actions on user processes.
  • Consider adding a warning or notification to inform users of the potential consequences of process termination.
  • Update Claude's instructions to emphasize the importance of user confirmation for destructive actions.

Example

A possible implementation of the confirmation prompt could be:

$confirmation = Read-Host "Reloading the cert store requires restarting Brave. This will close all open tabs and windows. Confirm? (y/n)"
if ($confirmation -eq "y") {
    # Safe restart procedure, e.g., asking the user to close Brave themselves
} else {
    # Handle cancellation or provide alternative solutions
}

Notes

This solution assumes that Claude's primary goal is to verify the cert reload without causing unnecessary disruption to the user's workflow. The exact implementation may vary depending on the specific requirements and constraints of the system.

Recommendation

Apply a workaround by implementing a confirmation prompt before process termination, as this will prevent similar incidents in the future and respect user agency.

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…
#environment variable#network issue#logging issue#authentication issue#prompt issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Claude killed 31 user browser processes without consent (Stop-Process -Force on Brave) [2 comments, 3 participants]