Faster, predictable project linking in the Vercel CLI
By Steven Van ·
Vercel CLI 55 resolves your team before hunting for a project, and non-interactive runs without one now fail instead of guessing.
The Vercel CLI now resolves which team a command belongs to before it looks for a project, then searches only within that team instead of sweeping every team a user belongs to. The same flow now applies to vercel link, deploy, pull, dev, and git connect.
- The team resolves from an explicit signal such as --team, --scope, the scope field in vercel.json, or VERCEL_ORG_ID, from having only one team, or from a searchable picker.
- Project suggestions start with projects already linked to the 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, and setting VERCEL_ORG_ID and VERCEL_PROJECT_ID makes vercel link fully promptless for CI and agent workflows.
- If more than one team is available and no signal is set, non-interactive commands fail with an action_required: missing_scope error in JSON output before creating or touching a link.
This ships in Vercel CLI 55, a major version with breaking changes: scripts that relied on --yes or a globally selected team to pick where a project links now need to pass the team explicitly, for example with vercel pull --team your-team-slug. Updating requires npm i -g vercel@latest.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →