Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.232 ·

Cross-session messaging refuses unsafe socket directories

If the socket directory for session-to-session messaging looks unsafe, messaging is turned off with a fix hint.

You'll notice New Features
JSON All of v2.1.232
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
New FeaturesKind: in v2.1.232,
New FeaturesSection of the release
What

Before creating the local socket directory that lets sessions talk to each other, Claude Code now inspects every component of that path and refuses to bind if it looks unsafe. When it refuses, cross-session messaging is simply off for that session rather than binding anyway, and you get a specific remediation hint.

Details
  • Rejected: symlinks owned by another user, path components that are not directories, world- or group-writable directories without the sticky bit, symlink chains deeper than 16 levels, and dangling links.
  • Each refusal is classified (directory_rule, foreign_owner, leaf_shape, raced, symlink_loop, and others) and the session records the cause socket_dir_refused and logs at error level.
  • The directory is created with mode 0700 and chmod'ed back to 0700 if found otherwise.
  • The suggested fix is to point XDG_RUNTIME_DIR or CLAUDE_CODE_TMPDIR at a private directory you own.
Evidence

Point XDG_RUNTIME_DIR or CLAUDE_CODE_TMPDIR at a private (0700) directory you own to use a different location.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.232 →

Feedback