Home › Guides

How to auto-fix failed Vercel builds with Claude

Deploy Center's Autofix checks for failed Vercel and Render builds every 10 minutes and hands each one, with the build log and secrets masked, to a Claude Code routine that fixes the error and opens a pull request. You review and merge the PR, then deploy the fix with one click.

Last updated 10 November 2026 · by Patrick Schmetzer, author of Deploy Center

1. Build fails
2. Claude Code routine
3. Fix PR
4. You merge
5. One-click deploy

What you need

• Deploy Center on a Mac, connected to Vercel and/or Render.
• A Claude Code routine at claude.ai/code with the repositories attached, and a cloud environment that can reach your package registries.

Set it up

1. Create the routine at claude.ai/code: Routines → New. Attach the repositories, pick the environment, and paste the prompt. deploys autofix prompt prints it, and the app has a button that copies it.
2. Add an API trigger in the routine: Trigger → + → API → Generate token. The token is shown once.
3. Give both to Deploy Center, in Settings → Autofix or in the terminal:

pbpaste | deploys autofix set-token      # token goes to the keychain
deploys autofix routine trig_XXXXXXXX

4. Try it without firing anything:

deploys autofix --dry-run

5. Run it every 10 minutes (installs a launchd job; off removes it):

deploys autofix schedule on

deploys autofix list shows every hand-over with its session link. The full reference is in docs/AUTOFIX.md.

What it does and does not do

• Fires for Vercel production deploys in ERROR and Render deploys in build_failed. Render runtime and health-check failures are only reported, because the build log does not show their cause.
• Never merges, never deploys. A person merges; you start the deploy.
• Rate limits: 2 hand-overs per project and 6 per account in 24 hours. No duplicates, and no new hand-over while a fix PR for that project is open.
• One attempt per fix. If the fix fails too, you get a notification instead of another round.
• Secrets are masked in the log when recognized. Masking is a help, not a guarantee: if your build logs may print secrets, do not use Autofix.

Honest limits

• The cloud session does not have your platform's environment variables, so a build can pass there and still fail on Vercel. Expect some PRs that do not fix the deploy.
• Causes outside the code, such as a missing secret, an expired key or a platform outage, cannot be fixed in a PR. Claude reports the cause instead.
• Detection runs while your Mac is awake. Every hand-over uses one routine run, including the ones that end in “nothing to fix in code”.
• The routines API is a research preview and may change.

Without Autofix: Copy for Claude

For a single failure, open the build log in Deploy Center and click Copy for Claude. It copies the project, commit and error lines as a fix request to paste into Claude Code.

Questions