{"version":"2.1.318","anchor":"project-read-falls-back-to-a-downloaded-file-when-the-origin","canonical_anchor":"project-read-falls-back-to-a-downloaded-file-when-the-origin","heading":"Oversized project files can be downloaded instead of failing, behind a server switch","tier":"notice","area":"Projects","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/project-read-falls-back-to-a-downloaded-file-when-the-origin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Oversized project files can be downloaded instead of failing, behind a server switch\n\nWhen a project file is too large to fetch directly, Claude Code can now download it as a local file with a notice, if a server switch allows it\n\n**What**\n\nWhen Claude Code reads a file from a project and the original is too large, it used to stop with an error. It now has a fallback: it downloads the file and hands back a copy saved on your machine, along with a notice. This fallback covers:\n\n- fetches that fail because the original or the upload is too large\n\n- files whose contents exceed the size limit, which before were simply reported as too big to keep\n\nThe fallback only runs when the remotely controlled setting `tengu_iterative_gray` allows it. When the server sends nothing, the code treats that setting as off, and the original error is shown as before.\n\n**Why**\n\nLarge project uploads become openable instead of failing, once the setting is turned on for an account.\n\n- Flag `tengu_iterative_gray`: Not enough to say (read for one account on one subscription tier against v2.1.318; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Projects\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}