Vercel
Test Vercel preview deployments before pull requests merge.
Vercel previews are a natural target for Autonomy pull request runs. The preview URL is the product surface reviewers care about, and Autonomy can verify real journeys against it before merge.
Setup
- Connect the GitHub repository in Autonomy.
- Connect the Vercel project that owns the preview deployments.
- Select the Autonomy plan that should run for pull requests.
- Add a protected preview bypass token if Vercel deployment protection is enabled.
- Open a pull request and confirm that Autonomy runs against the Vercel preview URL.
Why project selection matters
One GitHub repository can be connected to more than one Vercel project. Autonomy should only run against the selected project so it does not test the wrong preview deployment or publish evidence for an unrelated app.
Protected previews
If Vercel deployment protection blocks the preview URL, create a bypass token in Vercel and save it in Autonomy or your CI secret store. Autonomy uses the token only for the target preview host.
Troubleshooting
No PR run starts
Confirm the GitHub App is installed, the Vercel project is selected, and a preview deployment was created for the pull request.
The run opens a Vercel protection page
Add or refresh the bypass token and retry the run. Make sure the token belongs to the same Vercel project as the selected preview.