{"version":"2.1.300","anchor":"pdf-page-reads-capped-per-message-and-per-turn-after-context","canonical_anchor":"pdf-page-reads-capped-per-message-and-per-turn-after-context","heading":"PDF page reads can be capped per message and per turn once the context has filled","tier":"notice","area":"Read Tool","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/pdf-page-reads-capped-per-message-and-per-turn-after-context","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### PDF page reads can be capped per message and per turn once the context has filled\n\nTwo new env vars cap how many PDF pages Claude reads per message and per turn after the context has filled once\n\n**Unclear.** It is not clear what sets the enabled-and-enforced state, so setting the variables alone may not turn the limit on.\n\n**What**\n\nThe context is the amount of conversation Claude can hold at once. Once it has filled up one time, reading PDF pages can now be limited:\n\n- `CLAUDE_CODE_FILE_READ_MAX_PDF_PAGES_PER_MESSAGE` sets how many pages each of Claude's messages may read. The caps only apply when this is set below the normal per-request page maximum.\n\n- `CLAUDE_CODE_FILE_READ_MAX_PDF_PAGES_PER_TURN` sets the limit for a whole turn, with a built-in default if unset.\n\n- A per-session record must also say the feature is `enabled` and `enforced`, with its threshold within bounds.\n\n- A read over the limit is refused with a message starting 'The context has filled up once already', telling Claude to read fewer pages or answer from what it has and say which pages it did not reach.\n\nBefore, the only limit was the maximum page range per single request.\n\n**Why**\n\nAfter a long PDF has already filled the context once, Claude is pushed to answer with what it has rather than keep re-reading pages and filling the context again.\n\n- Area: Read Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}