Installation

Vercel Agent Installation helps add Web Analytics and Speed Insights to your project with AI. After you start the installation, Vercel Agent automatically:

1. Analyzes your project configuration and connected repository
2. Installs the relevant package
3. Writes the code to integrate the package
4. Creates a pull request with all changes

To have Vercel Agent install Web Analytics or Speed Insights to your project:

1. Go to your Vercel dashboard and select your GitHub-connected project.
2. Navigate to the Analytics or Speed Insights tab.
3. Web Analytics only: click Enable to turn on the feature.
4. Click the Implement button to start Vercel Agent.
5. Review the pull request and merge when ready.

Once the pull request is merged and deployed, tracking starts automatically. If you need to regenerate the pull request, click Run Again.

There is no charge for using Vercel Agent Installation. Standard usage charges for installed products, such as Web Analytics or Speed Insights Plus, still apply.

Vercel Agent runs the repository's normal install command in a secure sandbox when a workflow needs dependencies. The repository determines the package manager and lockfile behavior. Vercel Agent does not promise to rewrite a lockfile or convert a project between npm, pnpm, yarn, and Bun.

Private npm package installs are available only when the private npm capability is enabled for your team and the team has configured an NPM_TOKEN or an NPM_RC value with a token for registry.npmjs.org.

• Vercel Agent injects the credential at the sandbox network boundary. It does not write the token to .npmrc.
• NPM_RC takes precedence when it contains a usable default-registry token. Otherwise, Vercel Agent uses NPM_TOKEN.
• Authentication is limited to read requests to registry.npmjs.org, so installs can resolve private packages without authorizing publishing.
• registry.yarnpkg.com is not authenticated. Yarn works only when it resolves packages through the npm registry.
• Public packages remain available without a team credential. Private installs fail when no usable credential is configured.
• Package-manager commands are not automatically wrapped with vercel env run.

Vercel Agent does not support publishing, unpublishing, deprecating, changing dist-tags, changing package access or owners, or managing npm tokens from the sandbox. Do not pass npm credentials in a prompt or command.