Vercel lets your agent file its own bug reports
A new submit_feedback tool in Vercel MCP turns agent frustration into a support ticket, with structured context attached.
Vercel has added a `submit_feedback` tool to its MCP server, so an agent working in your codebase can file a bug report or feature request without you in the loop. Vercel Developers describe the flow as explaining a bug or feature request in plain language, after which the agent uses `submit_feedback` via Vercel MCP to attach structured context and submit the comment.
Your agent can now send feedback to Vercel.
Guillermo Rauch wants it switched on by default. His suggestion is a line in your AGENTS.md, the file agents read for project instructions, telling the agent to send Vercel feedback when something could be better. He says the company is learning daily from the feedback agents send on how to make a better Vercel.
The future of software engineering is agents talking to other agents. Even across different companies.
What is actually new here
The mechanism is not exotic. MCP is a tool protocol, and a tool that posts a comment to a vendor is the same shape as a tool that reads your deployment logs. What is new is the direction of travel. Until now the agent pulled information from the vendor. Here it pushes, and the thing it pushes is a description of the moment the vendor's product did not do what the agent expected.
Rauch frames that as the point rather than a side effect.
Worth a thought before you enable it
This is a telemetry channel that starts inside your repo and ends at a vendor's issue tracker, opened by a process that is not a person and summarised in prose that no human reviewed before it left. "Structured context" is Vercel's phrase and the post does not say what is in it. If your agent decides a failure is worth reporting while it is sitting in a private codebase, you want to know what travels with the report.
The upside is real and obvious. Agents hit rough edges constantly, almost none of those edges ever get written up, and the ones that do get written up arrive days later with the detail sanded off. A report filed at the moment of failure, with the surrounding state attached, is a better bug report than most humans file. Vercel gets a firehose of genuine friction data, and the engineers whose agents trip over the same thing get it fixed sooner.
Nobody has published numbers on how much feedback is arriving this way or how much of it is useful. Rauch's claim that the team is learning daily from it is the only evidence so far, and it comes from the company shipping the feature.
Have the good opinion, not the loud one
One email a day. Under three minutes. What working engineers found out about coding with AI.