Debug a Vercel App From Logs to Fix
For the production bug at 6pm. DuckyHelper pulls the runtime logs through Vercel's own API, reproduces the bug in its own browser tab with its own cursor, finds the code in GitHub, and opens a pull request you can review.
“Signups are failing in production. Check the Vercel logs, reproduce it, and open a PR with a fix.”
- 01Write small tools for Vercel and GitHub, onceSmall JavaScript tools made from how each site already works. The next run calls them directly.
getRuntimeLogs(deployment)getFile(path)createPullRequest(branch)
- 02Read the latest production errors
- 03Reproduce it in the browser with its own cursor
- 04Check the database for the failing query
- 05Find the line in GitHub and write a fix
- 06Open a pull request for your review
You getFrom "it's broken" to a pull request. You get the cause, the repro and a fix ready to review. It already knows your dashboards, so the next bug starts faster.
A run, drawn from this page · early access on Mac
Nothing to send, so it runs straight through.
Nothing in this job sends a message or pays for anything, so it works through to the end and tells you when it's done. If a step ever would, it's built to stop and ask you first.
If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.
Before you ask it.
What do I say?
Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud, in your own words, like "Signups are failing in production. Check the Vercel logs, reproduce it, and open a PR with a fix."
Why is the second time faster?
The first time, it writes small JavaScript tools for Vercel, GitHub and Supabase and builds an API from each site's own buttons, forms and requests. After that it calls them directly, so the job runs in one go instead of click by click. It costs less and breaks less.
Will it send anything without me?
It's built to ask first before it sends a message or pays for anything, and to wait for your yes. It may not recognize every send or payment, so keep an eye on tasks that involve messages or money. It's built not to type your passwords or card numbers: you sign in yourself, and it picks up from there.
Why not just do it by hand?
Debugging production means logs in one tab, the app in another, the code in a third, and keeping it all in your head.
Can I use this today?
Doing jobs in your apps is in early access on Mac. Talking to DuckyHelper, and having it see your screen and draw on it, works today on Mac, Windows and Linux.
- Early access
“Deploy the latest commit on main to production and tell me when it's live.”
Ship the Latest Commit and Watch the Build
See it run - Early access
“Check my Supabase project's health: schema, row security and anything that looks off.”
Check Your Supabase Database Is Healthy
See it run - Early access
“Give me a brief of PRs merged since yesterday and open PRs waiting on review.”
Morning Brief: PRs Merged and PRs Waiting
See it run
Do anything
Ask it a question or hand it a job, in any app.
Doing jobs for you is in early access on Mac. Asking works on Mac, Windows and Linux.