The Vercel CLI now resolves your team before discovering projects, then searches for projects only in that team instead of sweeping every team you belong to. Linking is faster and more predictable, and every command that establishes a link ( vercel link , deploy , pull , dev , and git connect ) follows the same flow:

Teams resolve from an explicit signal (such as --team , --scope , the scope field in vercel.json , or VERCEL_ORG_ID ), if you only have one team, or from a searchable picker.

Project suggestions begin with projects already linked to your local Git repository, then fall back to an exact folder-name match before opening up search and project creation across the team.

The --yes flag answers confirmations without ever selecting a team for you.

For CI and agent workflows, setting VERCEL_ORG_ID and VERCEL_PROJECT_ID makes vercel link fully promptless, while --team or --scope settles the team on any command.…