{"version":"2.1.208","anchor":"new-structured-error-types","canonical_anchor":"new-structured-error-types","heading":"New structured error types","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208\/e\/new-structured-error-types","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208","markdown":"### New structured error types\n\n**What**\n\nThree new error classes are introduced for cleaner error handling and telemetry:\n\n- `RipgrepNullByteError`: thrown when ripgrep is called with a null byte in its arguments\n- `RipgrepUsageError`: thrown when ripgrep rejects the pattern, glob, or file type filter without searching (previously these were untyped failures)\n- `SelectedRangeTooLargeError`: thrown when a requested line range exceeds the readable limit; the error message now names the limit and suggests searching for specific content instead\n- `BedrockUnexpectedContentTypeError`: thrown when a Bedrock streaming response has an unexpected content-type (not `application\/vnd.amazon.eventstream`); includes guidance to set `CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_GUARD=1` to suppress while a gateway is being fixed\n\n**Evidence**\n\nNew error classes (search for `\"RipgrepNullByteError\"`, `\"RipgrepUsageError\"`, `\"SelectedRangeTooLargeError\"`, `\"BedrockUnexpectedContentType\"`)"}