> ## Documentation Index
> Fetch the complete documentation index at: https://atcyrus.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy Previews

> How to use Vercel deploy previews to review Cyrus's changes end-to-end before merging.

When Cyrus opens a pull request, you want to verify the changes actually work — not just that the code looks right. Deploy previews give you a live environment to do exactly that.

***

## 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](/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

<Tip>
  Make deploy preview review a standard part of your workflow when Cyrus opens a PR. It takes seconds to open the link and is the fastest way to catch issues before they reach production.
</Tip>

***

## 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 member**

This 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

<Steps>
  <Step title="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.
  </Step>

  <Step title="Verify GitHub account connection">
    If the committer is already a team member but deployments still fail, ensure the GitHub account is correctly connected to the Vercel account. Go to **Settings → Authentication** in Vercel and confirm the GitHub connection is active.
  </Step>
</Steps>

<Warning>
  Both a valid [Git committer identity](/git-committer-identity) **and** Vercel team membership are required for deploy previews to succeed when commits are made by the Cyrus agent. Missing either one will prevent previews from being created.
</Warning>

<Note>
  If you've [customized the committer identity](/git-committer-identity#changing-the-committer-identity), make sure the updated identity is added to your Vercel team instead of the 'cyrusagent' user.
</Note>

***

## What's next

If deployments still aren't working after following these steps, reach out for help.

<Card title="Cyrus Community" href="https://discord.com/invite/prrtADHYTt" img="https://mintcdn.com/ceedaraiinc/75NMRUlNh03-gDHX/images/cyrus-f1.png?fit=max&auto=format&n=75NMRUlNh03-gDHX&q=85&s=947d2de0018937ce613572349bc91f06" width="1120" height="928" data-path="images/cyrus-f1.png">
  Get support on Discord
</Card>