Private/Stop-VerifiedProcess.ps1
|
# SPDX-License-Identifier: AGPL-3.0-or-later # Copyright (C) 2026 Tyler Vigario <# Stop processes matching a command-line pattern, re-verifying identity immediately before each kill. A pid recorded moments ago can already belong to something else. On 2026-07-29 a launcher exited between enumeration and termination and only this re-check prevented killing whatever had inherited its pid. Returns the number stopped. #> function Stop-VerifiedProcess { # No ShouldProcess here, for the same reason as Set-WindowVisible: the public # Restart-GreenroomSession gates the whole restart with one ShouldProcess call, so # gating each of the three kills separately would ask three times for one decision. [Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseShouldProcessForStateChangingFunctions', '')] [CmdletBinding()] [OutputType([int])] param( [Parameter(Mandatory)][string[]]$ProcessName, [Parameter(Mandatory)][string]$Pattern, [Parameter(Mandatory)][string]$Label ) $stopped = 0 # ProcessName may name more than one binary. An instance's watchdog and launcher run # under whatever shell was resolved -- pwsh.exe where pwsh 7 is present, powershell.exe # on stock Windows -- so both have to be matched. The command-line Pattern is the real # discriminator; the name is only a cheap pre-filter. $filter = ($ProcessName | ForEach-Object { "Name='$_'" }) -join ' OR ' $candidates = @(Get-CimInstance Win32_Process -Filter $filter -ErrorAction SilentlyContinue -Verbose:$false | Where-Object { $_.ProcessId -ne $PID -and $_.CommandLine -match $Pattern }) foreach ($p in $candidates) { $live = Get-CimInstance Win32_Process -Filter "ProcessId=$($p.ProcessId)" -ErrorAction SilentlyContinue -Verbose:$false if (-not $live) { continue } if ($live.CommandLine -notmatch $Pattern) { Write-Verbose "skipped pid $($p.ProcessId) -- no longer matches $Label" continue } Stop-Process -Id $p.ProcessId -Force -ErrorAction SilentlyContinue Write-Verbose "stopped $Label (pid $($p.ProcessId))" $stopped++ } return $stopped } <# Whether this process is running INSIDE the named instance's session. Walks up the ancestry looking for the claude.exe that owns this shell. Restarting an instance from inside itself kills an ancestor of the current process partway through, so the restart never reaches Start-ScheduledTask and the instance is left DOWN rather than restarted -- and running it from inside the session is the most natural way to invoke it, which is exactly what makes the trap worth a guard. #> function Test-SelfIsInstance { [CmdletBinding()] [OutputType([bool])] param([Parameter(Mandatory)][string]$Name) $esc = [regex]::Escape($Name) $ancestor = $PID for ($hop = 0; $hop -lt 8 -and $ancestor; $hop++) { $p = Get-CimInstance Win32_Process -Filter "ProcessId=$ancestor" -ErrorAction SilentlyContinue -Verbose:$false if (-not $p) { return $false } if ($p.Name -eq 'claude.exe' -and $p.CommandLine -match ('--remote-control\s+"?' + $esc + '("|\s|$)')) { return $true } $ancestor = $p.ParentProcessId } return $false } |