{"version":"2.1.286","anchor":"review-findings-arrive-in-session-attachment-download-failu","canonical_anchor":"review-findings-arrive-in-session-attachment-download-failu","heading":"Ultrareview findings can arrive in the session instead of a tracking link","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/review-findings-arrive-in-session-attachment-download-failu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Ultrareview findings can arrive in the session instead of a tracking link\n\nReview launches can pass findingsArriveInSession, and the launch message can say findings arrive here instead of giving a Track link\n\n**Unclear.** Whether a failed download is reported to Claude or to you some other way is not known.\n\n**What**\n\nUltrareview runs a code review in the cloud. A review launch now passes `findingsArriveInSession` set to true, which means the results are delivered back into your Claude Code session, the ongoing conversation.\n\n- The launch message no longer ends with `Track: <url>`. When `findingsArriveInSession` is set, it says \"The findings arrive here when it finishes.\"\n\n- Separately, when files attached to an incoming message cannot be downloaded, the fallback text `[N attached file(s) could not be downloaded]` is no longer added. The message prefix is used exactly as returned.\n\n**Why**\n\nYou wait for review results in the conversation instead of following a tracking link, which may no longer be shown. When an attachment fails to download, Claude no longer sees a notice about it.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}