Unsafe socket directories now name the owner, group and mode, and containers are detected.
What's wrong with this entry?
The check that vets the directory Claude Code uses for its local Unix sockets was reworked. Refusals now name the offending directory with its owner, group and mode and tell you how to fix it, and a container or sandbox where your uid is unmapped is now detected and refused explicitly instead of failing obscurely.
- New
uid_collapserefusal fires when running in a user namespace with no uid mapping, detected because your own uid reads back as the kernel overflow uid. The message suggests starting with a uid map, e.g.unshare -Ur. - Symlinked path components are resolved so real ownership is checked.
- A world-writable directory without the sticky bit suggests
chmod o-w. - Alternatives offered in every refusal: set
XDG_RUNTIME_DIRorCLAUDE_CODE_TMPDIR, or pass--messaging-socket-path.
start it with a uid map (e.g. unshare -Ur), or pass --messaging-socket-path
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.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross