{"version":"2.1.311","anchor":"project-texts-cut-to-fit-the-context-window-with-overflow-s","canonical_anchor":"project-texts-cut-to-fit-the-context-window-with-overflow-s","heading":"Long project texts are cut to fit and saved to files, and failed saves no longer fall back to inline text","tier":"notice","area":"Projects","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/project-texts-cut-to-fit-the-context-window-with-overflow-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Long project texts are cut to fit and saved to files, and failed saves no longer fall back to inline text\n\nBehind a flag, attached-project texts are trimmed with the rest saved to a file, and project docs that cannot be saved now fail instead of being inlined\n\n**Unclear.** It is not clear whether project_info's saving to a file is also behind the server-controlled setting or always applies.\n\n**What**\n\nWhen a project is attached to a session, its name, description and instructions (`prompt_template`) are sent to the model. This release changes how long project texts are handled:\n\n- Trimming (behind the `tengu_proud_firefly` flag, which has not been read): project name, description and `prompt_template` are cut to a size limit when they are too long. A note is added saying the `project_info` tool can provide a file holding the full text. Without the flag, the texts are sent whole.\n\n- `project_info` files: `project_info` now writes a long description and instructions to a `local_file`, splitting long lines at 450 characters. It now builds name, description and instructions with a shared helper.\n\n- Large project docs: reads of large project documents go to a `local_file`, and documents with very long lines are handled separately.\n\n- No more inline fallback: if saving a project document to a file fails, the helper now returns a failure (`not_stored` or `write_failed`). Before, it returned the whole document inline. The warning now reads `Projects tool: could not save a text of ${n} bytes to a file`.\n\n- Write guards: the `tengu_lovely_rain` and `tengu_toasty_owl` write guards are still behind flags. v2.1.310 built `tengu_lovely_rain` off by default; no reading has been taken for it under this release, and nothing has been read about `tengu_toasty_owl`.\n\n**Why**\n\nLarge projects take up less of the conversation's working memory, and the model is told where to find the rest. Watch for large document reads that now fail outright where they used to arrive in full.\n\n- Flag `tengu_proud_firefly`: Not enough to say (read for one account on one subscription tier against v2.1.311; 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: yes"}