{"version":"2.1.268","anchor":"github-not-connected-access-errors-for-cloud-review-restru","canonical_anchor":"github-not-connected-access-errors-for-cloud-review-restru","heading":"GitHub-not-connected \/ access errors for cloud review restructured with reusable builders","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/github-not-connected-access-errors-for-cloud-review-restru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### GitHub-not-connected \/ access errors for cloud review restructured with reusable builders\n\nGitHub-access error messages for cloud review reworked with dedicated builders and a faster inconclusive path\n\n**What**\n\nWhen `\/review`'s cloud review flow (`ultrareview`) can't find a GitHub account linked to your Claude account, or the linked account can't see the target repository, the error text is now assembled by dedicated helper functions instead of being built inline. The underlying check for GitHub access now has its own capped time budget, and it returns \"inconclusive\" immediately if the account isn't eligible, instead of always waiting on a full network call.\n\n**Why**\n\nThis should make these GitHub-access errors return faster and more consistently, particularly when the account clearly can't proceed, rather than always waiting out a full request.\n\n- Area: Elsewhere\n- Names: `\/review`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}