{"version":"2.1.228","anchor":"socket-paths-and-message-origins-redacted-in-debug-logs","canonical_anchor":"socket-paths-and-message-origins-redacted-in-debug-logs","heading":"Socket paths and message origins redacted in debug logs","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/socket-paths-and-message-origins-redacted-in-debug-logs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Socket paths and message origins redacted in debug logs\n\nDebug logs now mask socket paths, tokens and long hex values from local messaging.\n\n**What**\n\nDebug lines for the local socket client (`[uds-client] Sending control:` and `[uds-client] Sent to `) and peer-message origin summaries now run through the redactor that withholds anything matching \/token\/i and masks long hex runs, so raw socket paths and values no longer land in logs.\n\n**Details**\n\n- Detection of a dead agent socket widened: it now also recognises a typed error class in addition to ENOENT and ECONNREFUSED.\n\n**Evidence**\n\n`stale_socket`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}