Vercel
Overview
Capy detects Vercel preview deployments automatically and surfaces them in the pull request view. Review code diffs and the live preview side by side, with no webhooks, API keys, or configuration.
For an overview of Vercel previews in Capy, see Capy for Vercel.
How it works
When Vercel deploys a preview from a PR branch, Capy picks up the deployment from the PR's comments and its Vercel check, and shows a Preview button in the pull request view with the build state folded into it: ready, building, or failed.
The button links to the best available URL, in this order:
- A markdown link labeled "preview" in a PR comment beats a bare preview-host URL, and a stable
-git-branch alias beats a per-deployment URL. GitHub-hosted URLs never qualify. - The Vercel check's own details URL, when it points at the deployment rather than the vercel.com dashboard.
- As a last resort, the dashboard's inspect page for the deployment; one click from the preview beats a dead button.
With your Vercel project linked to GitHub, an agent's pull request triggers your Vercel preview deployment. Capy's Preview button opens the live deployment without additional configuration.


In-machine previews
For previewing during a thread before a PR exists, ask the agent to start your service and open it in the machine's browser, and watch the machine's desktop view live from the thread.
Full workflow
- Start an in-machine service so the agent validates changes while coding
- Agent opens a PR when done
- Vercel deploys a preview from the branch
- You review code and the live deployment from Capy's pull request view
Limitations
- Capy does not trigger Vercel deployments; your existing Vercel setup handles the deploy pipeline
- The Preview button shows one link per PR, the best-ranked one; other deployments stay reachable from Vercel