{"version":"2.1.271","anchor":"new-tip-relevance-check-helper-with-failure-telemetry","canonical_anchor":"new-tip-relevance-check-helper-with-failure-telemetry","heading":"New tip-relevance check helper with failure telemetry","tier":"internal","area":"Tips","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-tip-relevance-check-helper-with-failure-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New tip-relevance check helper with failure telemetry\n\nA new internal check confirms a tip is relevant before showing it, and logs failures instead of crashing\n\n**What**\n\nClaude Code has an internal helper that checks whether a 'tip' (a suggestion shown to the user) is actually relevant before displaying it. This involves checking that the tip has an `advertisedCommand` and passes a relevance check, then calling the tip's own `isRelevant` logic.\n\nIf any of that checking throws an error, the failure no longer crashes anything. Instead, the tip's id is recorded into a `failedTipIds` list and the error is logged.\n\n**Why**\n\nThis makes tip suggestions more resilient: a broken or misbehaving tip can no longer break the session, it just gets quietly skipped and noted for diagnosis.\n\n- Area: Tips\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}