Vercel CLI 55 is a major version bump with breaking changes. The core fix: the CLI now resolves your team first, then searches for projects only within that team. Every link-establishing command, vercel link, deploy, pull, dev, and git connect, follows this same flow. Team resolution comes from explicit signals in priority order: --team, --scope, the scope field in vercel.json, VERCEL_ORG_ID, a single-team account, or a picker.
The breaking part matters for CI and agent pipelines. If no team signal is set and more than one team exists, non-interactive commands now fail immediately with an action_required: missing_scope error in JSON output before touching anything. The --yes flag no longer silently picks a team for you. Scripts that relied on --yes or a globally selected team to determine where a project links will break. Fix: pass --team or --scope explicitly, or set VERCEL_ORG_ID and VERCEL_PROJECT_ID to make vercel link fully promptless.
The full change list is in the vercel@55.0.0 release notes on GitHub. What makes the full read worth it: the specifics on how project suggestions are ranked, starting with repos already linked to your local Git directory, then folder-name matches, then open search. Install with npm i -g vercel@latest.
[READ ORIGINAL →]