Using the PR action menu

When the ADO Pilot Marketplace extension is installed, a Run AI Review entry appears in the pull request action menu. Opening it does not start a new review — it opens an informational card explaining that reviews already fire automatically on every pull request create and update. To re-run a review, push a new commit to the source branch.

Where the entry appears

The Run AI Review entry is contributed under the pull request action menu — the three-dot overflow menu that hosts actions such as Mark as draft and Abandon. It is only visible when the ADO Pilot extension is installed in your organization. If you do not see it, see Installing and sharing the extension.

What you see when you open it

The entry opens a small dialog that renders one of three states based on whether ADO Pilot is configured for the organization.

Auto-reviews active

This is the normal state for an organization that has completed onboarding. The card displays:

ADO Pilot auto-reviews this pull request whenever it's created or updated. Push a new commit to re-run the review — no manual trigger is needed.

To regenerate credentials or view auth-failure reports, visit the adopilot.dev dashboard.

The "adopilot.dev dashboard" text links to https://adopilot.dev/dashboard and opens in a new tab. A Close button dismisses the dialog.

The card is intentionally informational. The extension does not have a path to manually trigger a review; the backend listens for git.pullrequest.created and git.pullrequest.updated events from your organization's service hooks and processes each event independently. Pushing a commit to the source branch generates a git.pullrequest.updated event, which is the supported way to ask for a fresh review.

Not configured

If the extension is installed but the organization has not yet completed onboarding, the card displays:

ADO Pilot is not configured for this organization.

Complete onboarding at adopilot.dev.

The "adopilot.dev" text links to the dashboard. There is no Close button on this state — close the dialog using the Azure DevOps dialog chrome. To resolve the state, open the adopilot.dev dashboard and finish the onboarding wizard.

Loading and error states

While the dialog is checking organization status it shows "Loading…". If the lookup fails, the card shows the error message and a Retry button. Retrying re-runs the same status check; if it keeps failing, the most likely causes are:

• The extension's stored organization settings were cleared and the extension cannot reach the backend to recover them.
• A transient Azure DevOps Extension Data Service outage. Wait a minute and retry.

If the error persists, open the adopilot.dev dashboard — the dashboard works independently of the extension and is the source of truth for review activity.

How to re-run a review

To re-run a review on an open pull request, push a new commit to the source branch. This generates a git.pullrequest.updated event that ADO Pilot processes the same way it processes the original create event. There is no other supported re-run path, and the action menu entry does not provide one.

If a review is failing repeatedly — for example because the PR is too large or because credentials have expired — re-running it without changing anything will not fix the underlying problem. Open the dashboard and check the auth-failure report or the review history for that pull request.

Frequently asked questions

Why doesn't the button just run a review when I click it? Earlier versions of the extension held an API key and called the backend directly. Since v0.1.8 the backend owns the subscription lifecycle, holds your PAT, and processes every PR event from your organization automatically. There is no longer a per-click code path; reviews are event-driven.

Can I disable the entry without uninstalling the extension? No. The entry is part of the extension's contributions; uninstalling the extension is the only way to remove it. See Uninstalling the extension.

Does opening the card cost a review credit? No. Opening the card only reads organization status — it does not call the review pipeline.