You'll notice
Useful3 Signal2
PowerShell profiles and hardware SSH keys are now treated as sensitive and won't be read or synced.
What's wrong with this entry?
Anonymous. No account, no email.
What
The checks that stop credential files being read or synced now recognise three PowerShell profile locations (documents/powershell/profile.ps1, the WindowsPowerShell variant, and .config/powershell/profile.ps1) and hardware-backed SSH keys whose names end in _ed25519_sk or _ed25519_sk_rk.
Details
- A new counter,
skipped_content_filter, was added to the breakdown of why files were skipped during sync, so content-filtered skips are distinguishable from other reasons. - Applies unconditionally.
Evidence
skipped_content_filter
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Claude checks a checkout's git configuration before running git in it
Both mention safety
-
v2.1.242
Wider detection of tampered git directories
Both mention safety
-
v2.1.242
Claude Code's git commands no longer recurse into submodules
Both mention safety