{"version":"2.1.290","anchor":"ccr-proxy-target-errors-are-sanitized","canonical_anchor":"ccr-proxy-target-errors-are-sanitized","heading":"Error details from a remote proxy are checked before use","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/ccr-proxy-target-errors-are-sanitized","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Error details from a remote proxy are checked before use\n\nClaude Code now drops error types and messages from a remote proxy if they look malformed or are too long\n\n**What**\n\nWhen a remote proxy that Claude Code talks to reports an error, Claude Code now checks the error details before using them. Before, it passed them through unchanged. The checks are:\n\n- the error type must be 1 to 64 letters, digits or underscores\n\n- the error message must be at most 1024 characters\n\nA value that fails is dropped, and Claude Code records that it left it out.\n\n**Why**\n\nError text from the other end of a connection cannot be trusted. Checking it first stops odd or oversized text from reaching the rest of Claude Code.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}