{"version":"2.1.311","anchor":"tool-results-inline-text-char-budget-can-force-cutting","canonical_anchor":"tool-results-inline-text-char-budget-can-force-cutting","heading":"Large tool output can be cut to fit a session's text budget","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/tool-results-inline-text-char-budget-can-force-cutting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Large tool output can be cut to fit a session's text budget\n\nSome sessions can now set how much tool output stays inline, cutting long output instead of saving it to disk\n\n**Unclear.** Which sessions supply this budget is not stated.\n\n**What**\n\nWhen a tool returns a lot of output, Claude Code usually tries first to save it to a file on disk. A tool is an action Claude takes, such as running a command or reading a file. A session can now supply a budget for how much text to keep in the conversation. When it does, Claude Code skips saving to disk and cuts the output. It keeps whichever is larger: the usual size limit or that budget.\n\n**Why**\n\nThis changes how large tool output is handled in sessions that set a budget.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}