Skip to main content
Revyl can hand proof of changes to Capy. When a pull request opens, Revyl starts a Capy thread in one of your Capy projects. The thread checks out the change, verifies it on a Revyl device, and reports back on the pull request.
Capy is in alpha. To add it to your organization, email [email protected].

​
What it does

  • Proves pull requests in Capy. With Capy as the proof agent, Revyl opens each pull request in a Capy thread. Capy verifies the change on a Revyl device and posts its write-up on the pull request, with a link to the thread.
  • Shows each run in Revyl. Capy runs appear under Cloud Agents → Proof of Changes next to Revyl and Cursor runs. A run’s Open in Capy opens its thread, and its Run logs show the thread’s transcript: the prompt, Capy’s messages, and the tools it called.

​
Setup

​
1. Connect Capy

Connect Capy under Integrations > Capy, and enable the Capy projects that check out your repositories.

​
2. Choose Capy for proof of changes

Turn on proof of changes for a Revyl project in a connected repository, then set its agent to Capy:
  • In the dashboard, open the GitHub integration page, select the repository and project root, then set the project’s Agent selector to Capy.
  • Or set the harness in .revyl/config.yaml:
Capy project is Automatic by default: the proof runs in the first enabled Capy project that checks out the repository. Pick one when several do. To choose the model, or to pin the project in YAML, see the harness fields in Proof of changes. A project can use its own Capy key instead of the organization default. In the project’s proof settings, click Use a separate Capy key for this project. Removing a project’s key sends its proofs back to the organization default.
  • Capy: connect Capy and manage the connection.
  • Proof of changes: how proofs run, their outcomes, and the harness fields.
  • GitHub: connect repositories and turn on proof of changes.