{"version":"2.1.236","anchor":"format-checks-for-message-ids-and-socket-paths","canonical_anchor":"format-checks-for-message-ids-and-socket-paths","heading":"Format checks for message ids and socket paths","tier":"internal","area":"Multi-Session","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/format-checks-for-message-ids-and-socket-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Format checks for message ids and socket paths\n\nMessages between Claude Code processes must now have well-formed ids and socket addresses.\n\n**What**\n\nNew validation for messages passed between Claude Code processes: an id must be `cc-msg-` followed by 32 hexadecimal characters, and a socket path must start with a `uds:`, `bridge:` or `did:` scheme. A separate check for loopback addresses was added nearby.\n\n**Evidence**\n\n`^(?:uds|bridge|did):`\n\n- Area: Multi-Session\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}