{"version":"2.1.299","anchor":"diagnostics-tail-snapshot-can-be-forced-by-a-caller","canonical_anchor":"diagnostics-tail-snapshot-can-be-forced-by-a-caller","heading":"Tail diagnostics can run without the diagnostics variable set","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/diagnostics-tail-snapshot-can-be-forced-by-a-caller","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Tail diagnostics can run without the diagnostics variable set\n\nThe tail diagnostics snapshot can now run when another part of Claude Code asks for it, even without CLAUDE_CODE_DIAGNOSTICS_FILE\n\n**Unclear.** No part of Claude Code is known to request the snapshot this way yet, so whether it runs without the variable is not known.\n\n**What**\n\nClaude Code's tail diagnostics snapshot used to run only when `CLAUDE_CODE_DIAGNOSTICS_FILE` was set. It can now also run when the part of Claude Code that calls it asks for it, even if that environment variable is not set.\n\n**Why**\n\nDiagnostics may be collected without the variable being set.\n\n- Area: Elsewhere\n- Names: `CLAUDE_CODE_DIAGNOSTICS_FILE`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}