Vercel integration

Preview deployments, right in Capy

When Vercel posts a preview URL on a pull request, Capy pins it next to the diff. Review the code, click through to the running app — nothing to configure.

Capy dangling down for a peek
Capy putting on glasses

Review the app, not just the diff

Preview URLs follow the work: live in the VM while coding, on the PR once Vercel deploys the branch.

Previews found automatically

Capy scans PR discussion comments for URLs with preview in the hostname and pins them to the PR toolbar. No webhooks, no API keys, nothing to set up.

Magnifying glass with a checkmark

PR comments → PR toolbar

Open the app from the review

Click Open preview in the PR view to reach the deployment Vercel built for that branch — the code and the running app, side by side.

Computer suspended by ropes

Any Vercel project connected to GitHub

Preview before the PR exists

Add a previews hook with your app's ports to .capy/settings.json, and agents check UI changes live in the VM while they're still coding. When the PR opens, Vercel deploys the branch and review picks up from there.

Tower of virtual machines

.capy/settings.json → previews

The preview rules at a glance

How Capy decides what to surface, and where it shows up.

Preview behavior

  • URLs read from PR discussion comments
  • One-click open from the PR toolbar
  • In-VM previews while coding
  • Multiple ports via .capy/settings.json
  • Any Vercel project connected to GitHub
  • No webhooks or API keys
  • First matching URL shown per PR
Capy gazing upward

Other integrations

The rest of the stack Capy connects to.

GitHub

Agents branch, commit, and open PRs. Main only moves through your merge process.

View integration

Slack

Tag @Capy in a thread and it becomes a task, with the conversation as context.

View integration

Linear

Delegate issues; team mappings and branch defaults route them to the right code.

View integration

FAQ

Setup, in-VM previews, and how detection works.

  • Do I need to configure anything?

    No. If Vercel is connected to your GitHub repo, Capy detects preview URLs from PR comments on its own — nothing to install or configure.

  • What about in-VM previews?

    For previewing during a task, before a PR exists, add a previews hook to .capy/settings.json with the ports your app runs on. Agents then validate changes live.

  • Does Capy trigger Vercel deployments?

    No. Capy reads the preview URLs Vercel posts on PR comments; your existing Vercel setup handles the deploy pipeline.

  • Can I see multiple preview URLs?

    Capy surfaces the first matching preview URL per PR. For in-VM previews, you can configure multiple ports for different services.

Ship changes you've already seen live

Previews appear on PRs on their own — review the code and the live app in one place.

Capys leaping through comic panels