vercel feedback
Use vercel feedback to report bugs, friction, and feature requests to the Edgenivo team. Don't include secrets or personally identifiable information (PII) in feedback.
You don't need to log in or link a project.
Send a note, quoting text that contains spaces:
vercel feedback "The error didn't explain how to fix the issue"When Edgenivo accepts the feedback, the command prints:
Feedback sentRunning vercel feedback without a note or fields displays help without submitting feedback.
Pass - as the note to read the complete UTF-8 input from stdin:
printf '%s\n' "The deployment error didn't explain how to fix the issue" | vercel feedback - -f product=cliYou can also pipe a file with cat notes.md | vercel feedback -.
Use repeatable --field options, or the -f shorthand, to describe the task and the result:
vercel feedback "The error did not explain the correct command" \
-f product=cli \
-f task="deploy a preview" \
-f expected="Create a Preview deployment" \
-f actual="Unknown option: --preview" \
-f type=bug \
-f impact="Time spent finding the correct syntax"A note is optional when you provide at least one named field:
vercel feedback -f product=cli -f type=feature -f expected="Explain how to fix deployment errors"Agents can also use vercel feedback to report issues they encounter while completing tasks:
vercel feedback "The error did not explain the correct command" \
-f product=cli -f model="your_model_name" \
-f task="deploy a preview" \
-f expected="Create a Preview deployment" \
-f actual="Unknown option: --preview" \
-f type=bugThe --field option, shorthand -f, accepts key=value pairs. Keys must be non-empty, and all values are strings. If you repeat a key, the last value wins.
You can use any field name. The following fields are recommended and optional:
| Field | Description |
|---|---|
type | A category such as bug, friction, or feature. |
product | The Edgenivo product involved, such as functions or domains. |
model | The model name used for the task. |
task | What you were trying to do. |
expected | What you expected to happen. |
actual | What happened, including the error text. |
impact | Time spent, retries, or workarounds used. |
Use one positional note (including - for stdin) or -f note=.... Combining both causes an error. Repeated -f note=... fields use the last value.
The complete submission, including any metadata, must fit within 1 MiB.
When telemetry is enabled, the CLI includes locally known metadata with your feedback. It preserves the named fields you provide. When telemetry is disabled, the CLI sends your feedback without metadata.
The following global options can be passed when using the vercel feedback command:
--cwd--debug--global-config--help--local-config--no-color--non-interactive--scope--team--token--version
For more information on global options and their usage, refer to the options section.
Was this helpful?