Connect Vercel

Connect Vercel once, and the Vercel CLI will be signed in on every Template box and devbox you use. Your terminals and coding agents can then run vercel commands without a separate vercel login on each devbox.

Connect Vercel

1. In the desktop app, open Integrations → Vercel and choose Connect Vercel.
2. Choose Open Vercel. Check that the code on Vercel matches the one-time code in boxes.dev. If Vercel lists a team, select it, then choose Allow Access.
3. Return to boxes.dev. The page will update on its own.

Vercel will describe the request as coming from the Vercel CLI on a device named boxes.dev. The location it shows will be a boxes.dev data center rather than where you are.

To check the connection, run vercel whoami in a terminal on any of your devboxes. It should print your Vercel username. boxes.dev doesn't install the Vercel CLI, so use the version your project already uses, such as npx vercel.

Sign in to SAML teams

If one of your Vercel teams requires SAML single sign-on, Vercel will ask you to sign in through your company's identity provider again when the team's SAML session ends. That's usually after a day, unless your company set a longer session.

On the Vercel page, these teams are listed under Teams that require SAML. Choose Sign in next to the team and finish your company's sign-in on Vercel. Then select the team and choose Allow Access. Every devbox will use the renewed sign-in.

If a vercel command on a devbox asks you to sign in for the team instead, you can follow its link. boxes.dev will share that sign-in with your other devboxes too.

Reconnect or disconnect

Running vercel logout on any devbox will end your Vercel sign-in everywhere. The Vercel page will then show Reconnect; choose it and approve the new code.

To stop using the integration, open the Vercel page's options menu and choose Disconnect Vercel. boxes.dev will delete your sign-in and sign the Vercel CLI out on every devbox.