{"version":"2.1.288","anchor":"session-transcript-write-emits-a-successrecovery-signal","canonical_anchor":"session-transcript-write-emits-a-successrecovery-signal","heading":"Claude Code records when saving the session history first works and when it recovers","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/session-transcript-write-emits-a-successrecovery-signal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Claude Code records when saving the session history first works and when it recovers\n\nClaude Code now records the first successful write of a session's history, and again when a failing writer recovers\n\n**Unclear.** It is not clear whether this event goes to usage reporting or only to a local diagnostics log.\n\n**What**\n\nClaude Code saves each session's conversation history, its transcript, to disk. It now records an event the first time that saving succeeds in a session. When the part that saves it had been failing and starts working again, the same event is recorded, marked as a recovery and noting what triggered it. Before, only the recovery was recorded, as a separate event.\n\n**Why**\n\nThis gives a health signal for whether session history is being saved.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}