The Vercel deployments nobody wants to work through
A companion works the 3 operations your Vercel account exposes. It can create a deployment and cancel a deployment, and every one of those waits on an approval card showing the deployment before it changes.
Open the deployment. Check it against something else. Write the change. Move to the next one. That is the Vercel afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a deployment until you approve it.
What it can do is exactly what Vercel exposes to an account you authorise and nothing beyond it: 3 operations, 1 read and 2 writes. In practice that means it can create a deployment and cancel a deployment.
The Vercel API stops at Vercel. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which Vercel deployments does a companion see?
1 of the 3 operations is a read.
Your account, not a guess at it: a companion can list deployments, and the full list below is the whole list, with nothing inferred from Vercel's documentation.
The deployments are what most of this inventory is about, alongside the deployments. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Vercel admin becomes a queue you review.
- List Deployments
Can it change a deployment without asking?
All 2 write operations wait for you.
A companion can create a deployment and cancel a deployment, and each one is staged on an approval card first: you see the deployment, the field and the new value before it lands in Vercel.
Nothing in Vercel is sent, changed or deleted on your behalf without that click, and a rejected card leaves the deployment exactly as it was. The gate is the same one on every surface, described at security.
- Create Deployment
- Cancel Deployment
Can it list deployments every morning by itself?
Yes.
Saved as a routine, the Vercel deployments pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Vercel deployments sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents