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
HomeReleasesv2.1.224entry #31

Claude Code v2.1.224 ·

Local messaging socket: where it lives, who can read it, and refusing to steal a live one

The messaging socket lives under XDG_RUNTIME_DIR with locked-down permissions and refuses to hijack a live one.

Use it now Notable No documentation found New Features
JSON All of v2.1.224
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
New FeaturesKind: in v2.1.224,
What probably matters to youSection of the release
What

The local socket used for session-to-session messaging binds under $XDG_RUNTIME_DIR/cc-socks/<pid>.sock, with the directory created 0700 and the socket 0600, and its path exported as CLAUDE_CODE_MESSAGING_SOCKET. If you pass --messaging-socket-path pointing at a socket something is already listening on, startup refuses rather than hijacking it.

Details
  • Falls back to a /tmp path, or $PREFIX/tmp under Termux, when the primary path would exceed the 103 byte limit on socket paths.
  • Non-local paths are refused outright.
  • Input is line-delimited JSON; any line over 1 MiB is dropped.
Evidence

--messaging-socket-path points to a live socket:

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

Read from
Names in the bundle--messaging-socket-pathCLAUDE_CODE_MESSAGING_SOCKETXDG_RUNTIME_DIR
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_MESSAGING_SOCKET

See this entry in the whole of v2.1.224 →

Feedback