{"version":"2.1.242","anchor":"corrupt-prompt-history-lines-are-skipped-rather-than-breakin","canonical_anchor":"corrupt-prompt-history-lines-are-skipped-rather-than-breakin","heading":"Corrupt prompt-history lines are skipped rather than breaking history","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/corrupt-prompt-history-lines-are-skipped-rather-than-breakin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Corrupt prompt-history lines are skipped rather than breaking history\n\nOne corrupt line in your prompt history no longer breaks history loading.\n\n**What**\n\nEach saved prompt-history line is checked against a schema; bad lines are dropped with a log entry naming the field and problem instead of derailing history loading.\n\n**Details**\n\n- Logs \"Skipping malformed history line\" and classifies each failure as a shape rejection or a parse failure.\n- Pasted-content attachments that had to be dropped from an otherwise valid line are counted.\n\n**Evidence**\n\n`Skipping malformed history line`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}