When a tool or platform trips up your coding agent, have the agent send the vendor a clear bug report with the task, what it expected and what actually happened: AI agent prompt
The agent that just hit a confusing error is the best placed to describe it. On Oct 23, 2026 Vercel added a submit_feedback tool to its MCP server and a vercel feedback command to its CLI, so coding agents can send bug reports, friction reports and feature requests straight to the Vercel team with structured context: the task, the expected behavior, what actually happened and the type of report. It only sends feedback when you ask, and Vercel's docs say to leave out credentials, secrets and full conversations. The prompt below turns that into a habit for any platform you use, with you approving every report.
The prompt
While you work on this project, keep a short list of any time a tool, API or platform we use ([Vercel, Supabase, Stripe, other]) blocked or confused you: unclear errors, wrong docs, missing features. At the end of the session, show me each one as a draft report with: the product, what you were trying to do, what you expected, what actually happened (the exact error message), the command or tool you used, and whether it's a bug, friction or a feature request. Remove any secrets, keys, customer data and private code before showing me. Don't send anything yourself. For each report I approve, send it through the vendor's official channel: for Vercel, the submit_feedback tool in the Vercel MCP or `vercel feedback "message" -f task=... -f expected=... -f actual=... -f type=bug`; for others, give me the issue text and the link to their feedback or issue page. Never send the same report twice.
Fill in the blanks, then copy
This prompt has 1 [bracket] to fill in. Type your details below and the prompt updates as you go. Your answers stay in this browser and are reused on other prompts with the same blanks. Nothing is sent to us.
Example values are fictional, just to show how a filled-in prompt reads. Replace them with your real details.How to use it
- Copy the prompt above.
- Replace every [bracket] with your own details (use the fill-in-the-blanks box above, which remembers your answers for the next prompt).
- Paste it into Vercel MCP, Vercel CLI, Claude Code and review the answer before you use it.
Works with: Vercel MCP, Vercel CLI, Claude Code, Cursor, Codex
Real-world example: vercel.com/changelog/send-feedback-from-vercel-mcp
Featured in: Free AI agent prompts for small business (beginner-friendly) · AI prompts for writing SOPs, reports, policies and checklists
Before you use it: what to check
Already built into this prompt
- Don't send anything yourself.
- For each report I approve, send it through the vendor's official channel: for Vercel, the submit_feedback tool in the Vercel MCP or `vercel feedback "message" -f task=...
- Never send the same report twice.
Check yourself
- Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings.
- Read and edit the draft before it reaches a customer or goes public. If you later automate this prompt, start with "draft and notify me", not "send automatically".
- Check names, dates, numbers and any claim against your own source material before you use the answer. AI can misread or invent details.
Using an AI agent? Download this prompt as a SKILL.md agent skill with these checks built in, or get the .zip for Claude.ai. How to install skills.
Want to make this prompt even better? Grade it with the free prompt grader or build your own with the AI prompt generator.
32 copy-paste agent prompts (PDF) plus 5 new prompts every week.
Get it free