Quick answer
Vercel’s July 21, 2026 announcement lists Vercel Agent for Pro and Enterprise teams and names three access surfaces: the Vercel Dashboard, GitHub, and Vercel CLI. Start in the Dashboard’s Agent section to confirm that the current team is eligible and enabled.
Do not assume that a personal account, Hobby project, consumer AI subscription, GitHub installation, or CLI login grants access. Check the exact Vercel team, project, plan, region, role, integration, pricing, and terms.
| Surface | Best for | Setup and governance check |
|---|---|---|
| Dashboard | Direct questions and production investigations | Team, project, environment, member role, task history, approval settings |
| GitHub | Pull-request review and fix handoff | App installation scope, repositories, branch protection, review and merge policy |
| CLI | Terminal-led investigation and project questions | CLI version, authenticated team, linked project, shell logging, local secrets |
The Vercel Agent product guide explains the product identity and trust model.
Verify access in the right order
- Sign in to the Vercel team that owns the target project.
- Confirm the team is currently on an eligible plan.
- Open the Agent section and check current feature enablement or enrollment.
- Select only the intended projects and environments.
- Review which members can create tasks and approve action plans.
- Connect GitHub only to required organizations and repositories.
- Authenticate the CLI to the intended team and linked project.
- Run a read-only evaluation before approving any action.
Plan labels and beta or rollout states can change. Capture the date, account, team, region, quoted price, included usage, overage treatment, retention, and support commitment from the live surface.
Dashboard access
Use the Dashboard for investigations where the reviewer needs visible production context and approval history. Before testing, separate production, preview, and development projects and confirm that users cannot accidentally target the wrong environment.
Test read-only questions first: what changed before an anomaly, which deployment correlates with an error, or which route caused a cost increase. Review cited logs and metrics rather than accepting an answer without source evidence.
GitHub access
Use GitHub when the expected output is a review comment or pull request. Restrict installation scope, preserve branch protection, require ordinary CI and review, and prevent the agent from merging solely because its own tests pass.
Confirm whether private repository contents, comments, issue data, secrets, or third-party actions enter the workflow. Apply the organization’s retention, access, and incident rules.
CLI access
Use the CLI when an engineer needs a terminal entry point. Verify the authenticated team and project before every sensitive task. Avoid placing secrets, customer data, or uncontrolled command output in prompts or logs.
CLI convenience does not expand authority. Vercel’s product announcement still describes the agent as read-only by default, with plan approval required for actions.
Pricing and procurement
The announcement establishes eligible team plans, not a durable standalone price or an unlimited entitlement. Before purchase, confirm:
- whether access is included or metered;
- task, token, compute, sandbox, or execution limits;
- failed and retried task treatment;
- seat, team, project, and region restrictions;
- support, audit, data-processing, and retention terms;
- cancellation, downgrade, renewal, and tax treatment.
Measure the cost per validated investigation or accepted fix, including human review and false-positive time.
Security baseline
Keep separate Vercel accounts and roles, least-privilege team access, scoped GitHub installation, branch protection, short-lived action approval, alerting, audit review, secret hygiene, rollback, and emergency disablement.
The production triage guide provides the operational approval sequence. This route does not establish any Vercel Agent integration inside Flowith.
Frequently asked questions
Which Vercel plans include Vercel Agent?
Vercel’s July 21, 2026 announcement lists Vercel Agent for Pro and Enterprise teams. Verify the live team plan, region, rollout, usage limits, price, support, and terms because a launch statement is not a permanent entitlement.
Where can I access Vercel Agent?
Vercel names the Dashboard, GitHub, and Vercel CLI. Each surface needs its own team, project, role, repository, authentication, logging, and permission checks.
Does a GitHub or CLI connection grant production action access?
No. Surface authentication does not replace Vercel Agent’s read-only default or plan approval. Confirm the intended team and project, review the named action, and preserve ordinary branch, deployment, and team controls.
Bottom line
Eligibility starts with a Pro or Enterprise Vercel team, but safe adoption depends on exact team, project, surface, role, integration, pricing, and data controls. Evaluate read-only behavior before granting a plan-scoped action.
Official sources
Source check: August 2, 2026. Verify the live Dashboard and current documentation before subscription, enablement, or access changes.