Vercel integration

Connect your project

You need an InstantWork board with a connected GitHub repository, a Codex connection assigned for coding tasks, and access to the Vercel project that deploys that repository.

1. Open Account → Connections and select Sign in with Vercel. InstantWork lists your Vercel projects that are linked to GitHub repositories.
2. On the board, open Board Details → GitHub & agents. Under Vercel, choose Use project next to the project that deploys the board's repository.
3. Under Previews & screenshots, keep Vercel as the preview provider. Set a production URL if you want to choose the baseline explicitly.

Vercel keeps previews behind deployment protection, so InstantWork's browser opens them with a Protection Bypass for Automation secret. When you choose a project, InstantWork creates a dedicated secret named “Instant Work screenshots” in the project through your Vercel connection. If Vercel doesn't allow that, it uses the project's existing automation bypass, or asks you to paste one from the project's Settings → Deployment Protection → Protection Bypass for Automation. The secret is stored encrypted and your previews remain protected.

Board Details shows a checklist: project connected, preview access secret saved, and protected previews open. All set means InstantWork has opened a ready preview with the secret. 1 step left means no preview has been checked yet; deploy one and select Check now, or wait for the next pull request preview.

What happens during a task

Jev decides whether a UI comparison would help demonstrate the change and whether to use screenshots or video. For eligible tasks, InstantWork captures the production baseline, then waits for a ready preview matching the pull request commit.

The browser repeats the same route and planned interactions on the preview. Available before-and-after media is posted together in InstantWork and linked from the GitHub pull request. Video export can fall back to screenshots. A capture failure is reported separately from the coding task.

The integration handles Vercel deployment protection. To capture pages behind your application's own login, add an agent sign-in route to your app; otherwise choose pages that do not require an account.

Agents and Vercel

Agents can work in Vercel through the same connection, using Vercel's MCP tools.

• Your private chat with an agent: it uses your own Vercel and every project you can reach.
• A board's chats: it uses the Vercel of the member who chose the board's project, and only that project. Calls about other projects or teams are refused.

Looking at projects, deployments and logs happens straight away. Anything that changes something, including deploys, settings, domains, environment variables and purchases, pauses with an approval card in the chat. In a board's chats any board editor can approve it; in a private chat only you can. Scheduled routines, board reviews and delegated work don't get Vercel tools, since nobody is there to approve.

Permissions and data

Projects

List your projects linked to GitHub repositories, and check the board's project still deploys its repository.

Deployments

Find a ready preview for the selected project and verify that it matches the pull request commit.

Project Protection Bypass

Create the dedicated automation bypass secret once, when you choose a project. InstantWork never revokes or changes your other secrets.

Your Vercel sign-in is held by Vercel Connect; InstantWork requests a short-lived token when it needs one and never stores it. Bypass secrets are encrypted in backend storage. Browser sessions run through Kernel cloud browsers; screenshots and exported videos are stored with InstantWork using Convex and shared through task messages and GitHub comments.

Captured content may become visible outside the preview's login protection, including through shared media links and public pull requests. Only capture information you are authorized to share with those audiences. See our Privacy Policy and integration EULA.

Manage or disconnect

Your Vercel connection stays yours. A board uses one member's Vercel project; any member who can edit the board can point it at one of their own projects, and the board owner can replace another member's. Other board members can run eligible coding tasks using it. That member or the board owner can remove it from Board Details.

Disconnecting Vercel in Account → Connections removes your projects from every board. Remove the “Instant Work screenshots” secret in the Vercel project's Deployment Protection settings to revoke it. Disconnecting does not delete media already posted to messages or pull requests.

Troubleshooting

Support