{"version":"2.1.321","anchor":"pdf-read-state-gets-a-left-behind-outcome-and-error-safe-c","canonical_anchor":"pdf-read-state-gets-a-left-behind-outcome-and-error-safe-c","heading":"PDF read tracking gains a \"left behind\" outcome and safer error handling","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/pdf-read-state-gets-a-left-behind-outcome-and-error-safe-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### PDF read tracking gains a \"left behind\" outcome and safer error handling\n\nClaude Code's tracking of PDF reads can now mark a PDF as left behind, and records the PDF anyway if a check fails\n\n**Unclear.** What difference this makes to a session that reads PDFs is not stated.\n\n**What**\n\nClaude Code keeps track of the PDF files Claude has read. Each read could already be marked as already written or as having no room. It can now also be marked as left behind.\n\nClaude Code also has new checks that decide whether a PDF Claude has not yet answered should be taken back out of that record. If one of those checks fails with an error, Claude Code logs the error and records the PDF anyway.\n\n**Why**\n\nThis is aimed at edge cases in how PDF attachments are handled. When a check goes wrong, the PDF stays recorded rather than being lost.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}