Unclear It is not clear whether project_info's saving to a file is also behind the server-controlled setting or always applies.
What
When 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:
- Trimming (behind the
tengu_proud_fireflyflag, which has not been read): project name, description andprompt_templateare cut to a size limit when they are too long. A note is added saying theproject_infotool can provide a file holding the full text. Without the flag, the texts are sent whole. project_infofiles:project_infonow writes a long description and instructions to alocal_file, splitting long lines at 450 characters. It now builds name, description and instructions with a shared helper.- Large project docs: reads of large project documents go to a
local_file, and documents with very long lines are handled separately. - No more inline fallback: if saving a project document to a file fails, the helper now returns a failure (
not_storedorwrite_failed). Before, it returned the whole document inline. The warning now readsProjects tool: could not save a text of ${n} bytes to a file. - Write guards: the
tengu_lovely_rainandtengu_toasty_owlwrite guards are still behind flags. v2.1.310 builttengu_lovely_rainoff by default; no reading has been taken for it under this release, and nothing has been read abouttengu_toasty_owl.
Why
Large 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.
tengu_proud_firefly Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.311: 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.
Read once, for one account on one subscription tier, against v2.1.311. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear whether project_info's saving to a file is also behind the server-controlled setting or always applies.
New in this build: tengu_proud_firefly