{"version":"2.1.248","anchor":"session-records-now-capture-how-a-session-ended","canonical_anchor":"session-records-now-capture-how-a-session-ended","heading":"Session records now capture how a session ended","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/session-records-now-capture-how-a-session-ended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Session records now capture how a session ended\n\nSession records now store how a session ended and where its working copy came from.\n\n**What**\n\nA git-backed session record can carry an `ended` block with a reason, a line of up to 2000 characters, a timestamp and whether it was published; a missing reason falls back to `ended_earlier`. Session starts also record where the working copy came from (`remote`, `bundle` or `overlay`) and whether it was seeded.\n\n**Details**\n\n- Non-git session records gained fields for tracked dependency directories, whether state is lost with the disk, and tombstones.\n- No gate; these fields are written whenever a session record is.\n\n**Evidence**\n\n`ended_earlier`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}