{"version":"2.1.268","anchor":"new-telemetry-events-for-the-verification-required-surface","canonical_anchor":"new-verification-required-api-error-surfaced-to-users-with","heading":"New \"verification required\" error message with tracking","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-telemetry-events-for-the-verification-required-surface","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New \"verification required\" error message with tracking\n\nA 403 verification_required API error now shows a dedicated message to users, with telemetry for when it and its link are shown\n\n**What**\n\nClaude Code now recognizes a specific kind of 403 error response from the API: one whose body indicates `error.type: 'permission_error'` with `details.error_code: 'verification_required'`. Instead of falling through to a generic error message, this is turned into a distinct `verification_required` error result that shows the server-provided message directly to the user.\n\nTwo new telemetry events, `tengu_ranch_rc_shown` and `tengu_ranch_rc_link_shown`, were added and fire when this verification-required message (and, separately, its link) are shown. The `tengu_ranch_rc_shown` event only fires the first time this happens.\n\n**Why**\n\nThis gives users a clear, specific explanation when their account or request needs verification, instead of a generic error, and lets Claude Code track how often users encounter this situation.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}