{"version":"2.1.287","anchor":"deep-link-opener-reports-timeout-and-oversized-output","canonical_anchor":"deep-link-opener-reports-timeout-and-oversized-output","heading":"Failed deep links now say whether the opener timed out or printed too much","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/deep-link-opener-reports-timeout-and-oversized-output","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Failed deep links now say whether the opener timed out or printed too much\n\nWhen opening a deep link fails, Claude Code now reports a timeout or too much output, and its link-handler check is no longer limited to `claude` links\n\n**Unclear.** It is not clear which link types other than `claude` are now checked.\n\n**What**\n\nA deep link is a web link that opens Claude Code directly. When the program that opens such a link fails, Claude Code now reports two more causes: that it \"timed out\", or that it \"printed too much output\".\n\nThe check for which program on your system handles these links also changed. Before, it only looked for the handler of `claude` links. It now checks whichever link type it is given.\n\n**Why**\n\nWhen a deep link does not open, the message now gives a more specific reason, which makes the problem easier to track down.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}