Under the hood
Useful2 Signal3
A cyber-refusal mitigation now sticks after you resume a session instead of being forgotten.
What's wrong with this entry?
Anonymous. No account, no email.
What
The refusal-fallback record now carries a sticky flag, sawCyberRefusal, merged forward each time the fallback state is updated. On resume, the mitigation header is re-applied if either the current refusal category or the sticky flag says cyber, so it still applies after the original categorised event has scrolled out of the conversation.
Details
- Serialised as
saw_cyber_refusal.
Evidence
sawCyberRefusal
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