{"version":"2.1.295","anchor":"tool-read-context-exposes-signal-pdfrendersignal-and-filere","canonical_anchor":"tool-read-context-exposes-signal-pdfrendersignal-and-filere","heading":"Tools that read files receive different background information","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/tool-read-context-exposes-signal-pdfrendersignal-and-filere","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Tools that read files receive different background information\n\nThe information passed to Claude Code's file-reading tools now includes stop signals and reading limits, and drops three older items\n\n**Unclear.** It is not clear whether this changes anything a user can see when Claude reads files.\n\n**What**\n\nWhen one of Claude Code's tools reads a file, it is handed some background information about the current request. That information has changed.\n\nIt now includes:\n\n- a signal that tells the tool to stop if the request is cancelled\n\n- a separate stop signal for turning PDF pages into images\n\n- limits on how much of a file may be read\n\nIt no longer includes:\n\n- a record of whether a git diff was read\n\n- information about where a permission prompt is shown\n\n- a marker for whether the user changed the content\n\n**Why**\n\nThis is a change to how Claude Code passes information to its tools internally. It may not change anything you see.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}