Source: vercel.com/changelog/evaluate-vercel-flags-from-another-project-without-sharing-sdk-keys
Previously, sharing flags between projects meant copying a server SDK key into an environment variable and managing it by hand. With Project Connections, connected projects authenticate using their deployment's identity, and local development uses the OIDC token that vercel env pull retrieves.
Access is managed from the Connections page under a project's Flags section, or with the vercel flags connections command in the CLI. The consumer deployment determines which flag environment is evaluated, so production deployments read production flags.
To use a shared flag, a consumer application creates an adapter with the source project's ID through @flags-sdk/vercel, then attaches it to a flag definition. Project Connections are available on all plans and require @flags-sdk/vercel 1.6.0 or later, or @vercel/flags-core 1.11.0 or later, with Vercel CLI 63.0.0 or later for CLI management.
Why it matters if you build agents
Agents and services that read flags from another project no longer need a long-lived server SDK key stored in an environment variable, which removes a credential to rotate and protect.
Access can be removed from the Connections page or the CLI without a redeploy, so teams can cut off a consumer project quickly.
Check the minimum package and CLI versions before relying on connections, since older @flags-sdk/vercel releases will not support them.
Get stories like this every weekday
One short email with the day's agent tooling news.