{"version":"2.1.242","anchor":"pdf-reads-inside-repl-results-are-capped-with-an-explicit-no","canonical_anchor":"pdf-reads-inside-repl-results-are-capped-with-an-explicit-no","heading":"PDF reads inside REPL results are capped with an explicit note","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/pdf-reads-inside-repl-results-are-capped-with-an-explicit-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### PDF reads inside REPL results are capped with an explicit note\n\nToo many PDFs in one REPL result get dropped with a note telling Claude to read fewer.\n\n**What**\n\nWhen Read calls made inside a REPL produce more PDFs than the result can carry, the extras are dropped and replaced by a note that states the cap and tells Claude to read fewer PDFs per call, so the model can correct itself instead of silently losing documents.\n\n**Details**\n\n- Parallel counters were added for omitted images and for image pages that failed to render.\n\n**Evidence**\n\n`\"type\": \"text\"`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}