{"version":"2.1.248","anchor":"crashed-sessions-write-a-structured-diagnostic-line-to-the-t","canonical_anchor":"crashed-sessions-write-a-structured-diagnostic-line-to-the-t","heading":"Crashed sessions write a structured diagnostic line to the transcript","tier":"notice","area":"Error Handling","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/crashed-sessions-write-a-structured-diagnostic-line-to-the-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Crashed sessions write a structured diagnostic line to the transcript\n\nA crashed non-interactive session writes a structured diagnostic line into the transcript.\n\n**What**\n\nWhen a non-interactive session throws, the transcript now gets a line naming the error, its API status and its cause alongside the raw messages, and in some modes the user sees a short \"Session crashed\" message instead of the raw error text.\n\n**Details**\n\n- The line is prefixed `[session_crash]` and starts with `error_name=`.\n- Which sessions get the short form rather than the raw error is decided by a session check in the crash path.\n\n**Evidence**\n\n`[session_crash] error_name=`\n\n- Area: Error Handling\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}