Skip to main content
The easiest way to get Proof of Changes running is the GitHub App. This guide covers the alternative: setting up Proof of Changes with a Cursor Automation when you can’t install the GitHub App, or you use a different SCM provider.

​
Who this is for

This guide is for teams that:
  • Already build every PR in their own CI (GitHub Actions or equivalent)
  • Already use Cursor Automations
  • Want a device-backed proof comment on the PR
  • Haven’t connected the Revyl GitHub App yet

​
What happens on each PR

If no matching build exists, the Automation comments that proof was not run and stops — it never rebuilds and never claims proof without a device session.

​
Getting started

​
1. Install Revyl in Cursor

Install the Revyl plugin and authenticate.

​
2. Add an upload step to CI

After your existing build produces a simulator .app or installable .apk, upload it:
See the ready-made upload-for-cursor-proof.yml workflow in the public CLI examples. It stores REVYL_API_KEY as a CI secret and the app id as a variable; GitHub Actions metadata (scm_head_sha, PR number, and related fields) is stamped automatically so the Automation can match the build to the commit.

​
3. Enable the Cursor Automation

Create an Automation at cursor.com/automations:
  1. Paste the prompt from PROMPT.md.
  2. Enable Comment on pull request and shell. Do not enable Revyl MCP.
  3. Trigger CI completed / Workflow run completed on the upload job. Do not use Pull request pushed as the default.
  4. Add secret REVYL_API_KEY and variable REVYL_APP_ID.
Full trigger and identity notes: AUTOMATION_SPEC.md.