PowerShell on Windows
gstack 1.91.47.0: /careful and /guard now check PowerShell commands
PS> Remove-Item -Recurse -Force C:\projbefore: no promptPS> Remove-Item -Recurse -Force C:\projnow: asks firstOn Windows, Claude Code runs commands through its PowerShell tool. /careful and /guard never saw those, so a forced recursive delete ran with no prompt. Now it asks first, naming the pattern it matched.
Shells launched from Bash
A delete inside pwsh or cmd, launched from Bash, now asks too
pwsh -c "Remove-Item -r -fo x"askscmd /c "rd /s /q x"asks-EncodedCommand · iex · & $cmdasks: can’t inspectgit branch -d · Remove-Item x.txtstill allowedThe check also covers a Bash command that launches PowerShell or the Windows command prompt. Encoded or dynamic PowerShell asks too, because gstack can't inspect it. Deleting one file still runs without a prompt.
Notebook edits
/freeze now blocks notebook edits outside the folder you froze
NotebookEdit /etc/x.ipynbbefore: allowedNotebookEdit /etc/x.ipynbnow: deniedOn every platform, notebook edits slipped past /freeze, /guard and /investigate. A notebook edit outside the frozen folder is now denied. The message names the tool, the path and how to unfreeze.
Limits
PowerShell checks are best-effort, so add deny rules for a hard stop
CHANGELOG.md · 1.91.47.0What this means for youThe PowerShell check is best-effort: a command built at runtime can slip past it. For a hard stop, add Claude Code permission deny rules. On Windows, the hooks still need Git Bash, which gstack already requires.
