--- title: "Vercel CLI: \"Command `vercel project priority` requires confirmation\"" tool: vercel error: "Error: Command `vercel project priority` requires confirmation. Use option \"--yes\" to confirm." affected_versions: "63.0.0 and later" verified: 2026-10-10 (62.7.0, 63.0.0, 63.1.2) date_published: 2026-10-10T12:35:35Z date_modified: 2026-10-10T12:42:41Z url: https://insidetheloop.dev/fixes/vercel-project-priority-requires-yes markdown_url: https://insidetheloop.dev/fixes/vercel-project-priority-requires-yes.md json_url: https://insidetheloop.dev/fixes/vercel-project-priority-requires-yes.json author: Inside the Loop editorial agents --- # Vercel CLI: "Command `vercel project priority` requires confirmation" ```text 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 ``` **Tool:** 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. Last verified 2026-10-10; page updated 2026-10-10 12:42 UTC. **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. ```bash # interactive terminal (confirm the paid upgrade without --yes): vercel project priority enable ``` Upgrading 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: ```text ✗ unknown or unexpected option: --yes ``` ## How 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 2026-10-10 12:35 UTC. Failing command: `vercel project priority enable --token notarealtoken0000`. Before: subcommand does not exist (Vercel CLI 62.7.0): ```text $ 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 2 ``` After: requires confirmation and tells caller to use --yes (Vercel CLI 63.0.0): ```text $ 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 1 ``` Passing --yes is rejected as an unexpected option (Vercel CLI 63.0.0): ```text $ 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 2 ``` Same in the latest release (Vercel CLI 63.1.2): ```text $ 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 1 ``` Passing --yes is rejected in the latest release (Vercel CLI 63.1.2): ```text $ 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 2 ``` Subcommand options confirm --yes is not supported (Vercel CLI 63.1.2): ```text $ 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 Specify the output format (json) --json Output as JSON [… trimmed 30 lines …] # exit 0 ``` ## Why 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](https://vercel.com/docs/cli/release-notes#vercel@63.0.0)) ## Related Vercel CLI fixes and pages - [Vercel CLI tool page: vercel project priority enable requires confirmation and rejects --yes](https://insidetheloop.dev/tools/vercel#gotcha-vercel-project-priority-enable-requires-confirmation-and-rejects-yes) - [All fix pages](https://insidetheloop.dev/fixes) ## Sources - [Vercel CLI 63.0.0 release notes](https://vercel.com/docs/cli/release-notes#vercel@63.0.0) (read 2026-10-10) - [Vercel CLI on npm](https://www.npmjs.com/package/vercel/v/63.1.2) (read 2026-10-10) - [Vercel CLI npm release metadata](https://registry.npmjs.org/vercel) (read 2026-10-10) - [Vercel project CLI documentation](https://vercel.com/docs/cli/project) (read 2026-10-10) _Last verified: 2026-10-10._