Skip to main content

​
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.

​
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:
  1. 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.
  2. The Vercel check’s own details URL, when it points at the deployment rather than the vercel.com dashboard.
  3. As a last resort, the dashboard’s inspect page for the deployment; one click from the preview beats a dead button.
1

Connect your repo

Link your Vercel project to GitHub. When Vercel deploys previews on PRs, Capy detects them automatically.
2

Agent opens a PR

An agent works on your thread and opens a PR. Vercel triggers a preview deployment from the branch.
3

Preview in Capy

Click Preview in the pull request view to open the live deployment.
No configuration is required. If Vercel is connected to your GitHub repo, it just works.

​
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

  1. Start an in-machine service so the agent validates changes while coding
  2. Agent opens a PR when done
  3. Vercel deploys a preview from the branch
  4. 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

​
FAQ

No. If Vercel is connected to your GitHub repo, Capy detects previews from PR comments and the Vercel check automatically. There’s nothing to install or configure.
No. Capy reads preview links but doesn’t trigger deployments. Your existing Vercel setup handles the deploy pipeline.
Previews still appear: the Vercel check’s details URL and the dashboard inspect page are fallback sources, so the comment lane isn’t required.
The Preview button surfaces the single best link per PR. For multiple running services during a thread, the machine’s Desktop services menu discovers in-machine HTTP services automatically.