{"version":"2.1.225","anchor":"sdk-spawn-errors-carry-a-telemetry-class-and-redacted-paths","canonical_anchor":"sdk-spawn-errors-carry-a-telemetry-class-and-redacted-paths","heading":"SDK spawn errors carry a telemetry class and redacted paths","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/sdk-spawn-errors-carry-a-telemetry-class-and-redacted-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### SDK spawn errors carry a telemetry class and redacted paths\n\nLaunch failure reports now scrub secrets out of file paths before sending them.\n\n**What**\n\nExecutable launch failures and subprocess init timeouts now report a structured error class, and any path in the message is scrubbed for secrets before it is interpolated.\n\n**Details**\n\n- The helper producing \"executable not found \/ failed to launch\" strings now returns an object with `telemetryMessage` and `errorClass`, one of \"executable_launch_failed\" or \"executable_not_found\".\n- Paths go through a new redaction helper applying the shared token patterns: Bearer, sk-ant-, AKIA, gh*_, JWT and others.\n- Subprocess init timeouts become a TelemetrySafeError with errorClass \"initialize_timeout\"; the user-visible message is unchanged.\n\n**Evidence**\n\n`errorClass: \"initialize_timeout\"`\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}