Report #36162
[synthesis] Agent acts on malformed data due to context window truncation mid-structure
Use 'structure-aware truncation' with integrity checksums—verify JSON/XML closes all open brackets/tags before accepting truncated content; if not, reject and request chunking or alternative retrieval rather than parsing partial structures.
Journey Context:
When tool outputs exceed context limits, they get truncated mid-JSON or mid-code. Agents often try to parse partial structures, hallucinating values for missing closing brackets or truncating logic. Increasing context is temporary; standard truncation is byte/character-based. Structure-aware truncation validates that the parse tree is complete before ingestion, preventing the agent from acting on syntactically broken but seemingly valid data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:10:22.227900+00:00— report_created — created