Return the URL, don't block

Deploy with --no-wait, hand back the URL, check it with inspect.

From deploy-to-vercel, SKILL.md “Output”.

When does the user get a link?

Press Deploy. The build takes about a minute and a half.

Wait for the buildBad
vercel deploy -y
URL now, status afterGood
--no-waitthenvercel inspect

vercel deploy [path] -y --no-wait        # prints the URL at once
vercel inspect <deployment-url>          # Building → Ready
vercel inspect <deployment-url> --logs   # if the build fails

# After a git push: newest entry in "deployments"
vercel ls --format json

# Report the URL and its status. Don't curl it to "verify".

Why it matters, pros and cons

Why it matters

Builds take minutes, but the URL exists from the first second. Give it, then read the status.

Pros

  • The user has the link right away.
  • inspect reports the real state and logs.
  • The agent isn't stuck on a long build.

Cons

  • The link shows a build page until ready.
  • You must check the status; don't curl the URL.