Skip to main content

​
Overview

Capy detects Vercel preview deployments automatically from PR comments and surfaces them in the dashboard. Review code diffs and live previews side by side, no webhooks or API keys needed.

​
How it works

When Vercel deploys a preview from a PR branch, it posts a comment with the preview URL. Capy scans PR comments for URLs with preview in the hostname and surfaces the first match in the PR toolbar.
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 task and opens a PR. Vercel triggers a preview deployment from the branch.
3

Preview in Capy

Capy detects the preview URL from the PR discussion. Click Open preview link in the PR view to see the live deployment.
No configuration is required. If Vercel is connected to your GitHub repo, it just works.

​
In-VM previews

For previewing during a task before a PR exists, add a previews hook to .capy/settings.json with the port numbers your app runs on. Agents can then validate UI changes in real time from the task interface.
.capy/settings.json
{
  "previews": [
    {
      "port": 3000,
      "name": "Web app"
    }
  ]
}
You can configure multiple ports for different services (e.g., frontend on 3000, API docs on 8080).

​
Full workflow

  1. Configure in-VM previews 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 PR view

​
Limitations

  • Only the first matching preview URL per PR is surfaced
  • Capy does not trigger Vercel deployments — your existing Vercel setup handles the deploy pipeline
  • Preview detection relies on Vercel’s PR comments; if comments are disabled, previews won’t appear

​
FAQ

No. If Vercel is connected to your GitHub repo, Capy detects preview URLs from PR comments automatically. There’s nothing to install or configure.
No. Capy reads preview URLs from PR comments but doesn’t trigger deployments. Your existing Vercel setup handles the deploy pipeline.
Currently, Capy surfaces the first matching preview URL from PR comments. For in-VM previews, you can configure multiple ports for different services.