{"version":"2.1.295","anchor":"resume-diagnostics-reporter-active-only-with-claude-code-di","canonical_anchor":"resume-diagnostics-reporter-active-only-with-claude-code-di","heading":"Diagnostics file can now record how a resumed conversation was loaded","tier":"use","area":"Diagnostics","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/resume-diagnostics-reporter-active-only-with-claude-code-di","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Diagnostics file can now record how a resumed conversation was loaded\n\nWith CLAUDE_CODE_DIAGNOSTICS_FILE set, Claude Code writes a report on how each resumed conversation was loaded from its saved transcript\n\n**What**\n\nThe diagnostics file set with `CLAUDE_CODE_DIAGNOSTICS_FILE` can now capture a `resume_load_report` record. Claude Code writes it when you resume an earlier conversation and reloads its saved history, called the transcript. The record notes:\n\n- the last saved row of the transcript\n\n- which rows were left out\n\n- details about forks and checkpoints in the conversation\n\n- whether fetching the full history, and any changes since, succeeded\n\nA separate check records whether a result could be sent back, with answers such as `tail_too_old` or `process_dequeued_a_command`.\n\nNone of this runs unless `CLAUDE_CODE_DIAGNOSTICS_FILE` is set. Without it, nothing is recorded.\n\n**Why**\n\nThis gives a detailed trail for tracking down problems with resuming conversations and with how a turn finished. It has no effect on normal use.\n\n- Area: Diagnostics\n- Names: `CLAUDE_CODE_DIAGNOSTICS_FILE`, `resume_load_report`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}