{"version":"2.1.269","anchor":"agenttask-description-and-reason-fields-are-now-sanitized-a","canonical_anchor":"agenttask-description-and-reason-fields-are-now-sanitized-a","heading":"Agent\/task description and reason fields are now sanitized and length-capped","tier":"internal","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/agenttask-description-and-reason-fields-are-now-sanitized-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Agent\/task description and reason fields are now sanitized and length-capped\n\nAgent and task description\/reason fields are now cleaned up and capped at 1024 characters, and tool-use IDs must match a strict pattern\n\n**What**\n\nSeveral internal fields used when spawning a subagent, running a background bash task, or setting a scheduled reminder or loop are now run through a sanitizer before use:\n\n- `description` and `reason` strings have control characters and unusual formatting characters stripped, extra whitespace collapsed, and leading\/trailing whitespace trimmed\n\n- these strings are now truncated to 1024 characters, with an ellipsis added if they were cut off\n\n- `toolUseId` fields (identifiers used to track a specific tool call) must now match a strict pattern of letters, numbers, and the characters `_`, `.`, `:`, `-`, up to 128 characters, instead of being accepted as any string\n\n**Why**\n\nThis prevents malformed, oversized, or oddly-formatted text from leaking into internal descriptions and reasons, and closes off invalid tool-use identifiers from being accepted where a stricter format was always intended.\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}