Read Vercel deployment evidence in Context
Connect deployment revisions, environments, state, and freshness to the projects and tasks they prove.
Project and task Context can now show Vercel deployment evidence: preview, staging, or production environment; deployment state; exact revision when verified; provider time; and observation freshness. Inspector links open the matching Vercel deployment.
Connect a team and map its project
A workspace owner or admin starts in Settings → Integrations → Vercel deployments. Copy the proposed callback URL into a Vercel account webhook, then enter its secret, a team-scoped API token, the Vercel project, and a verified GitHub repository. Atoll checks the numeric repository identity before it saves encrypted credentials. Reconcile deployments reads a bounded recent page and reports incomplete or truncated results.
Keep each fact tied to its evidence
A deployment links to a task only when one task in the mapped project has a PR link with the exact repository and SHA. An older revision does not validate a newer head. Production supersession follows the latest authenticated production target, including rollback to an older build. Preview and staging remain separate. Missing identity stays unavailable.
Agents read these records through the existing External Reference CLI and MCP tools. This integration does not deploy, promote, roll back, move tasks, or grant human acceptance. Disable removes stored credentials and marks evidence unavailable while preserving history. Unlink removes an association; a later verified update can restore it.