Vercel CLI Adds a Feedback Command for Developers and Coding Agents
Vercel has added a `vercel feedback` command to its CLI, letting users send bug reports, friction reports and feature requests to the Vercel team directly from the terminal. Coding agents can use it too, attaching structured context when they hit problems.
- The Vercel CLI now includes a `vercel feedback` command for bugs, friction reports and feature requests.
- Coding agents can send feedback too, using the -f or --field flag for key=value context.
- Fields in Vercel's example cover product, model, harness, task, expected, actual and type.
- Feedback can be piped in from a file with `cat notes.md | vercel feedback -`.
- Users need to update to the latest Vercel CLI to get the command.
What the new command does
According to Vercel's changelog, the Vercel CLI now includes vercel feedback, a command that routes bugs, friction reports and feature requests to the Vercel team without leaving the terminal. The simplest use is to pass a message as a string. The changelog gives the example of a user reporting that an error did not explain how to fix the issue.
The aim is to shorten the path between running into a problem and telling the company about it. Instead of switching to a browser or another tool, a developer can describe the issue at the moment it happens, in the same place where the command failed.
Structured feedback for coding agents
Vercel says coding agents can also send feedback when they run into issues. For this, the command accepts the -f or --field flag, which adds structured context as key=value pairs. The flag can be repeated so the report describes the task, the expected behavior and what went wrong.
The example in the changelog sets several fields on one report:
- product: cli
- model: gpt-6-astra
- harness: fx
- task: deploy a preview
- expected: Create a Preview deployment
- actual: Unknown option: --preview
- type: bug
In that sample, the message says the error did not explain the correct command, and the fields record that the task was deploying a preview and that the CLI returned an unknown option error instead.
Piping longer notes
The changelog also shows that feedback can be read from standard input. Running cat notes.md | vercel feedback - sends the contents of a file as the feedback message. This allows longer write-ups, such as notes collected during a debugging session, to be submitted without retyping them into the command line.
What it means for users
For developers using the Vercel CLI, the change adds a built-in way to report problems and request features. For people who work with coding agents, the field options give those agents a defined format for describing what they attempted and where it failed, including which model and harness were involved, based on the fields shown in the example.
To use the command, Vercel says to update to the latest Vercel CLI and read the vercel feedback documentation. The changelog does not give details on how feedback is handled after submission.
Vercel: Send feedback from the Vercel CLI
