{"version":"2.1.323","anchor":"diagnostics-log-for-skipped-duplicate-user-messages","canonical_anchor":"diagnostics-log-for-skipped-duplicate-user-messages","heading":"Diagnostics log now records skipped duplicate copies of your messages","tier":"use","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/diagnostics-log-for-skipped-duplicate-user-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Diagnostics log now records skipped duplicate copies of your messages\n\nWith CLAUDE_CODE_DIAGNOSTICS_FILE set, Claude Code now logs each time it skips a follow-up copy of a message you already sent\n\n**What**\n\nSometimes the same message you typed can reach Claude Code more than once. Claude Code skips the later copy. When the `CLAUDE_CODE_DIAGNOSTICS_FILE` environment variable is set, Claude Code now writes a line to that diagnostics file each time it skips one of these copies. An environment variable is a named value you set in your shell before starting Claude Code.\n\nEach line records:\n\n- whether Claude had already started replying after the original message\n\n- what kind of copy was skipped\n\nIf Claude Code cannot work out whether Claude had already started replying, it writes no line for that copy.\n\n**Why**\n\nThe log helps track down messages that seem to be duplicated or lost, especially in remote sessions, where Claude Code runs somewhere other than your own computer.\n\n- Area: Elsewhere\n- Names: `CLAUDE_CODE_DIAGNOSTICS_FILE`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}