{"version":"2.1.248","anchor":"remote-bash-spawn-errors-are-redacted-before-being-shown","canonical_anchor":"remote-bash-spawn-errors-are-redacted-before-being-shown","heading":"Remote bash spawn errors are redacted before being shown","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-bash-spawn-errors-are-redacted-before-being-shown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote bash spawn errors are redacted before being shown\n\nRemote bash spawn errors are sanitised before they appear in the transcript.\n\n**What**\n\nWhen a remote bash command fails to start, the error text now passes through a session-aware sanitiser instead of being interpolated raw into the tool result.\n\n**Details**\n\n- The `input_remote_bash` and `spawn_failed` telemetry pair is unchanged.\n\n**Evidence**\n\n`spawn_failed`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}