You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Code ReviewArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release
What
The failure message shown when a cloud /code-review run fails no longer always tells the user to retry /code-review ultra or fall back to local review. It now branches on the specific failure reason, such as session_archived, stopped_remotely, or session_not_found, only recommending the ultra/local retry for a subset of causes.
Whether a poll that repeatedly gets 404s is treated as session_not_found versus just a timeout is now controlled by a remote-config flag, tengu_breezy_diffie.
Why
This gives clearer, more accurate next steps when a cloud code review fails, instead of always pointing to the same generic retry advice regardless of the actual cause.
