Source: vercel.com/changelog/vercel-sandbox-now-supports-managed-npm-credentials
Vercel Sandbox can now install a team's private npm packages using credentials kept in its Shared Environment Variables. Custom registries, including GitHub Packages and JFrog Artifactory, are also supported. Developers turn this on by passing credentials with npm set to true when they create a sandbox.
The tokens stay outside the sandbox. Vercel's firewall adds authentication to install requests sent to the registries a team has configured, so a coding agent can install dependencies without ever seeing the tokens.
To use the feature, update the @vercel/sandbox SDK or the CLI to the latest version, for example with pnpm add @vercel/sandbox@latest. Vercel points to its npm credentials documentation for setup details.
Why it matters if you build agents
Agents that need private packages no longer need registry tokens written into the sandbox or passed through their prompts. Builders should upgrade the SDK or CLI before relying on the flow. Project files still have to be copied into the sandbox before the install runs.
Get stories like this every weekday
One short email with the day's agent tooling news.