{"version":"2.1.281","anchor":"bridge-debug-logs-hash-ids-and-sanitise-values","canonical_anchor":"bridge-debug-logs-hash-ids-and-sanitise-values","heading":"Bridge debug logs hash IDs and sanitise values","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bridge-debug-logs-hash-ids-and-sanitise-values","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Bridge debug logs hash IDs and sanitise values\n\nBridge debug logs now hash work and session IDs and hide JSON values and unusual type or mode text\n\n**What**\n\nThe bridge, the part of Claude Code that talks to a remote service, writes debug logs. Debug logs are detailed records used for troubleshooting. They now hide more:\n\n- Work-poll lines that carry a `mode` show workId and sessionId as `sha12:` hashes, a scrambled short code, instead of the real IDs.\n\n- type and mode are written only if they are short, plain text (letters, digits, `_`, `.` and `-`, up to 64 characters). Anything else is written as `<type>`.\n\n- The WebSocket input line now replaces JSON values with \"[REDACTED]\".\n\n**Why**\n\nDebug logs are often shared when reporting problems. These logs now leak fewer identifiers and less message content."}