How It Works
When Cyrus pushes a commit to a pull request branch, Vercel automatically creates a deploy preview — a live, shareable URL running the latest version of your changes. Because Cyrus uses a dedicated Git committer identity, you can immediately tell which deploy previews were triggered by agent commits versus human commits.Reviewing the Agent’s Work
Deploy previews are the primary way to review Cyrus’s changes end-to-end. Rather than only reading diffs, open the deploy preview to verify the agent’s work behaves correctly in a real environment. Use deploy previews to:- See the full result of the agent’s work in a live environment
- Catch visual or functional issues that aren’t apparent from code review alone
- Share preview links with teammates for faster feedback
- Test interactions and flows before merging into your main branch
When It Doesn’t Work
If the Cyrus Git committer is not a member of your Vercel team, deploy previews will fail with an error like:Vercel deployment failed: cyrusagent not a team memberThis happens because Vercel requires the commit author to be a recognized member of the team that owns the project. Even though the commit is valid and pushed to GitHub, Vercel will reject the deployment if it cannot associate the committer with a team member.
How to Resolve
Add the Cyrus committer as a Vercel team collaborator
In your Vercel dashboard, go to Settings → Members and add the Cyrus committer (by default,
cyrusagent) as a collaborator on the appropriate team.If you’ve customized the committer identity, make sure the updated identity is added to your Vercel team instead of the ‘cyrusagent’ user.
What’s Next
If deployments still aren’t working after following these steps, reach out for help.
Cyrus Community
Get support on Discord

