{"version":"2.1.228","anchor":"local-socket-messaging-sanitized-logs-and-unused-auth-state","canonical_anchor":"local-socket-messaging-sanitized-logs-and-unused-auth-state","heading":"Local socket messaging: sanitized logs and unused auth state","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/local-socket-messaging-sanitized-logs-and-unused-auth-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Local socket messaging: sanitized logs and unused auth state\n\nLocal socket logs now scrub addresses and unexpected message values before printing.\n\n**What**\n\nThe local unix-socket channel between Claude Code processes now routes unhandled control actions and message types through the error logger with values passed through a sanitizer, and sanitizes the socket address it prints during namespace checks.\n\n**Details**\n\n- The server object gained auth fields: `authRequired`, `activeTokens`, `activeKeyFile`, `authOkReported`, `authDropReported`, `lastStartFailureCause` and `lastStartDegradedCause`, all cleared on teardown.\n- `authRequired` comes from a `requireAuth` start option; nothing in this build passes it, so token auth on this channel is inert here.\n\n**Evidence**\n\n`[uds-messaging] Unhandled control action: `\n\n- Area: Cross-Session Messaging\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}