vercel
Vercel Deployment Guide
Deployment Protection and Agent Access
Vercel deployments may have Deployment Protection enabled, which requires authentication to access preview deployments. This can block automated testing and agent access to preview URLs.
Identifying Protected Deployments
If you encounter a login page or authentication requirement when accessing a Vercel preview URL, the deployment has protection enabled. Signs include:
- Redirect to
vercel.com/loginor SSO login page - 401/403 errors when accessing the deployment
- Preview URLs that require Vercel team membership
Enabling Agent Access with Protection Bypass
To allow agents and automated systems to access protected deployments, users need to set up Protection Bypass for Automation:
- Navigate to Project Settings
- Go to the Vercel Dashboard
More from openhands/extensions
deno
If the project uses deno, use this skill. Use this skill to initialize and work with Deno projects, add/remove dependencies (JSR and npm), run tasks and scripts with appropriate permissions, and use built-in tooling (fmt/lint/test).
19init
Create an AGENTS.md contributor guide for a repository (or a subdirectory) following a concise, repo-specific template. Use when the user runs /init.
17bitbucket
Interact with Bitbucket repositories and pull requests using the BITBUCKET_TOKEN environment variable. Use when working with code hosted on Bitbucket or managing Bitbucket resources via API.
16github-pr-review
Post PR review comments using the GitHub API with inline comments, suggestions, and priority labels.
16pdflatex
Install and use pdflatex to compile LaTeX documents into PDFs on Linux. Use when generating academic papers, research publications, or any documents written in LaTeX.
15github
Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUB_TOKEN environment variable and GitHub CLI. Use when working with code hosted on GitHub or managing GitHub resources.
15