Source: vercel.com/changelog/vercel-ci-no-longer-requires-a-linked-vercel-project
Until now, running Vercel CI on a repository meant creating an empty Vercel project to link it. Vercel says that step is no longer needed. Setup requires the Vercel GitHub App installed with access to the repository, a GitHub account connected to a Vercel account, and write or admin permission on the repository.
To enable it, run the vercel ci enable command from a clone of the repository. CI is turned on for the team the CLI is set to, and the --scope flag selects a different team. From the next push onward, tasks run as configured in the repository.
Support is limited to private GitHub repositories, and public repositories and other Git providers are not yet supported. The changelog points to the Vercel CI documentation for configuring tasks.
Why it matters if you build agents
Agent projects in private GitHub repositories can get CI runs without a placeholder Vercel project, which simplifies setup for automated pipelines.
Public repositories and other Git hosts still cannot use this path, so those agent projects need another approach for now.
Check the GitHub App access and repository permissions before scripting the enable step across many repositories.
Get stories like this every weekday
One short email with the day's agent tooling news.