{"version":"2.1.318","anchor":"project-docs-can-be-injected-as-a-synthetic-tool-round-behi","canonical_anchor":"project-docs-can-be-injected-as-a-synthetic-tool-round-behi","heading":"Project documents can reach Claude as a plain message, behind a switch","tier":"soon","area":"Projects","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/project-docs-can-be-injected-as-a-synthetic-tool-round-behi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Project documents can reach Claude as a plain message, behind a switch\n\nA switch lets project documents reach Claude as a plain message instead of a pretend tool call, and PDFs from messages get their own handling\n\n**What**\n\nWhen Claude Code gives Claude your project's documents, it has always presented them as if Claude had called a tool to read them. A switch can now make Claude Code send them as a plain background message holding the document contents. The switch is off unless it is turned on remotely, and it does not apply when an option asks for the documents to be sent the old way.\n\nTwo related changes:\n\n- PDF contents read from messages now have their own way of being shown to Claude.\n\n- When files are held back, Claude Code adds a line saying how many were held back.\n\n**Why**\n\nThis changes the form in which project documents and PDFs reach Claude, which can affect how Claude treats them.\n\n- Area: Projects\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}