Local socket logs now scrub addresses and unexpected message values before printing.
What's wrong with this entry?
The 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.
- The server object gained auth fields:
authRequired,activeTokens,activeKeyFile,authOkReported,authDropReported,lastStartFailureCauseandlastStartDegradedCause, all cleared on teardown. authRequiredcomes from arequireAuthstart option; nothing in this build passes it, so token auth on this channel is inert here.
[uds-messaging] Unhandled control action:
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