[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Vercel deployment blocked for Cursor Agent co-authored commits on Hobby team

121 views · 1 like · 1 post


Glavin001 (@glavin001) · 2026-03-09 · ♥ 1

## Observed

I am seeing the following error during deployment:

> **Deployment Blocked**
> The Deployment was blocked because the commit author does not have contributing access to the project on Vercel.
> Hobby teams do not support collaboration. Please upgrade to Pro to add team members.

And:

> **@cursor-agent** is attempting to deploy a commit to the `glavin001`’s projects team on Vercel, but is not a member of this team.

For PR: [https://github.com/Glavin001/ShipyardAI/pull/144](https://github.com/Glavin001/ShipyardAI/pull/144)  
My commits show: `cursor-agent` and `Glavin001` as co-authors.

## Expected

Vercel documentation states that `Cursor Agent` shouldn't count as a member—it is just me:

! [Vercel](https://vercel.com/changelog/claude-code-and-cursor-agent-no-longer-require-a-team-seat)

!

### [Claude Code and Cursor Agent no longer require a team seat - Vercel](https://vercel.com/changelog/claude-code-and-cursor-agent-no-longer-require-a-team-seat)

`Claude Code` and `Cursor Agent` can now trigger builds on Vercel without a team seat, as a part of our bot detection policies.