Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
File AccessArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release
What
Claude Code tests whether the system supports O_NOFOLLOW_ANY, an option for opening files. It records the answer as noFollowAny. The answer is now always saved:
EINVAL error: recorded as "rejected"
any other error: recorded as "works"
Before, only EINVAL saved an answer, and any other error left it blank.
Why
The check now always ends with a stored answer, where before it could be left empty after an unexpected error.
