Open Brain
VercelEngineering PostOfficial Source

Send feedback from the Vercel CLI

The new vercel feedback command lets developers and coding agents report CLI friction with structured task, expectation, and failure context directly from the terminal.

Vercel · Oct 23, 2026
Open Source Open MarkdownOpen JSON
Source Summary

The latest Vercel CLI adds **vercel feedback** for sending bug reports, friction reports, and feature requests from the terminal. It accepts a message directly or content piped through standard input.

Practical Implication

Coding agents can attach structured context using repeatable **--field key=value** arguments. Include the attempted task, expected behavior, and actual result so automated reports remain actionable rather than becoming unstructured transcripts.

Agent-Ready Context
The latest Vercel CLI adds **vercel feedback** for sending bug reports, friction reports, and feature requests from the terminal. It accepts a message directly or content piped through standard input.

Coding agents can attach structured context using repeatable **--field key=value** arguments. Include the attempted task, expected behavior, and actual result so automated reports remain actionable rather than becoming unstructured transcripts.

The command only submits feedback; the material does not describe issue tracking, response times, privacy handling, or automatic remediation. Agents should still avoid placing credentials or sensitive project data in reports.
Connected Context · Feed7 Judgment

This adds a structured outbound feedback path to Vercel’s expanding agent-friendly CLI surface. It complements CLI-based changelog discovery and operational control by letting terminal agents report failures and friction, but it does not close the loop through tracking or remediation. The repeatable fields make reports more actionable while preserving the need to filter sensitive context.

Context Map
toolscoding#coding-agents#dev-ux#tool-use
Uncertainty
The command only submits feedback; the material does not describe issue tracking, response times, privacy handling, or automatic remediation. Agents should still avoid placing credentials or sensitive project data in reports.