Faster, More Predictable Project Linking in Vercel CLI

Vercel CLI has been updated to identify the team first before finding the project, providing a much faster and more predictable linking experience than the previous approach of scanning through all teams. Now all linking-related commands such as vercel link, deploy, pull, dev, and git connect follow the same flow.

The new workflow has the following characteristics:

• Team identification: The team is determined first via --team, --scope, the scope field in vercel.json, or VERCEL_ORG_ID. For single-team users, a searchable selector is provided.
• Project suggestion: Projects already linked to the local Git repository are suggested first, followed by a check for folder name matches, and then the process moves on to searching for and creating projects within the team.
• CI/CD optimization: Setting VERCEL_ORG_ID and VERCEL_PROJECT_ID allows vercel link to run without any separate prompts.

This Vercel CLI 55 release is a major update that includes Breaking Changes. If existing scripts relied on the --yes flag or a globally configured team, they must now explicitly pass the team using the --team flag.