Finding / gemini-cli

2026-10-13-gemini-cli-tool-text-fields-gain-a-non-configurable-65536-byte-cap

Tool text fields gain a non-configurable 65536-byte cap. A 65,536-byte cap now applies to individual handled text strings, parts and response fields in the truncation path. It is not an aggregate ceiling on every result: two 40 KB text parts can both survive, binary/non-plain objects are outside the recursive string treatment, and experimental context management takes a separate distiller branch. A truncated field keeps its head with the explanatory suffix inside the byte budget. Saving the original is best-effort; disk errors are swallowed and some calls have no saved path. The old truncateToolOutputThreshold setting cannot raise this constant. The PR’s 512 KB/50,000-token compression watermark is not implemented; compression uses a configured fraction of model context, default 0.5. The compression service also protects three recent tool turns and reduces older eligible responses to 2 KB previews, with retrieval exceptions.

Channel: tagged-release. Half: both. Date: 2026-10-06.

Operator consequence: Re-test large file/web/MCP text fields and workflows that previously raised or disabled truncation. Paginate or explicitly preserve full output outside model history when completeness matters. Check that a saved path exists before relying on it; a truncation note is not a durable receipt. The cap bounds handled text without promising either an aggregate payload budget or recoverable omitted content.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-gemini-cli-tool-text-fields-gain-a-non-configurable-65536-byte-cap

Profile citations

Source links

Primary links, including exact changelog lines when available.