Vercel CLI: "Command `vercel project priority` requires confirmation"
Vercel CLI 63.1.2 (Node.js 24.21.0)
Error: Command `vercel project priority` requires confirmation. Use option "--yes" to confirm.
Error: Link project errorTool: Vercel CLI (vercel, vc). Versions: Affected: 63.0.0 and later; last version without this error: 62.7.0; we reproduced it on 62.7.0, 63.0.0, 63.1.2. Exit code 1.
Cause: Vercel CLI 63.0.0 (released 2026-10-08) added vercel project priority; in a non-interactive run from an unlinked directory, the link guard suggests --yes, but the priority subcommand does not accept that flag and enabling Priority still requires interactive confirmation.
Fix: Run vercel project priority enable in an interactive terminal without --yes, or enable Priority in the Vercel dashboard.
# interactive terminal (confirm the paid upgrade without --yes):
vercel project priority enableUpgrading to Priority adds a paid feature that incurs billing charges on the account, so Vercel deliberately disallows non-interactive confirmation. The CLI option parser for vercel project priority only accepts --format and --json. If an automated agent or CI run encounters this error, do not pass --yes; direct the human user to run vercel project priority enable interactively from a linked directory, pass the project name if it is not linked, or enable Priority in Project Settings on the Vercel Dashboard.
The same cause also prints:
✗ unknown or unexpected option: --yesHow did we reproduce the Vercel CLI error?
A fresh Linux container from bin/sandbox-run (Node.js 24.21.0, root, online, no credentials for any service), destroyed after the run. Run on . Failing command: vercel project priority enable --token notarealtoken0000.
Before: subcommand does not exist (Vercel CLI 62.7.0):
$ vercel project priority enable --token notarealtoken0000
Vercel CLI 62.7.0 (Node.js 24.21.0)
Error: Please specify a valid subcommand: inspect | list | members | accessGroups | add | access-summary | checks | protection | update | rename | remove | token | speedInsights | webAnalytics | pause | dangerously-delete-immutable-static-asset | observability | resume
[… trimmed 94 lines …]
# exit 2After: requires confirmation and tells caller to use --yes (Vercel CLI 63.0.0):
$ vercel project priority enable --token notarealtoken0000
Vercel CLI 63.0.0 (Node.js 24.21.0)
Error: Command `vercel project priority` requires confirmation. Use option "--yes" to confirm.
Error: Link project error
# exit 1Passing --yes is rejected as an unexpected option (Vercel CLI 63.0.0):
$ vercel project priority enable --yes --token notarealtoken0000
Vercel CLI 63.0.0 (Node.js 24.21.0)
✗ unknown or unexpected option: --yes
Vercel CLI 63.0.0 accepts: --api, --cwd, --debug, --format, --global-config, --help, --json, --local-config, --no-color, --non-interactive, --scope, --team, --token, --version.
# exit 2Same in the latest release (Vercel CLI 63.1.2):
$ vercel project priority enable --token notarealtoken0000
Vercel CLI 63.1.2 (Node.js 24.21.0)
Error: Command `vercel project priority` requires confirmation. Use option "--yes" to confirm.
Error: Link project error
# exit 1Passing --yes is rejected in the latest release (Vercel CLI 63.1.2):
$ vercel project priority enable --yes --token notarealtoken0000
Vercel CLI 63.1.2 (Node.js 24.21.0)
✗ unknown or unexpected option: --yes
Vercel CLI 63.1.2 accepts: --api, --cwd, --debug, --format, --global-config, --help, --json, --local-config, --no-color, --non-interactive, --scope, --team, --token, --version.
# exit 2Subcommand options confirm --yes is not supported (Vercel CLI 63.1.2):
$ vercel project priority --help
Vercel CLI 63.1.2 (Node.js 24.21.0)
▲ vercel project priority action [name] [options]
Upgrade a project to Priority, or remove that upgrade
Options:
-F, --format <FORMAT> Specify the output format (json)
--json Output as JSON
[… trimmed 30 lines …]
# exit 0Why does Vercel CLI print this error?
The 63.0.0 release notes introduce "vercel project priority enable to upgrade a project to Priority interactively in the terminal" because upgrading to Priority incurs billing charges; while ensureLink prompts headless environments with a generic message suggesting "--yes", the priority subcommand options schema only defines --format and --json and intentionally lacks --yes. (Vercel CLI 63.0.0 release notes)
Related Vercel CLI fixes and pages
- Vercel CLI tool page: vercel project priority enable requires confirmation and rejects --yes
- All fix pages
Sources
- Vercel CLI 63.0.0 release notes (read 2026-10-10)
- Vercel CLI on npm (read 2026-10-10)
- Vercel CLI npm release metadata (read 2026-10-10)
- Vercel project CLI documentation (read 2026-10-10)
Last verified: 2026-10-10.