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

# Proof via Capy

> Let Capy prove your pull requests on Revyl devices

Revyl can hand [proof of changes](/agents/proof) 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.

<Note>
  Capy is in alpha. To add it to your organization, email [support@revyl.ai](mailto:support@revyl.ai).
</Note>

Prompt for your coding agent:

```text
Set this repository's Revyl proofs to run in Capy.

Read https://docs.revyl.com/integrations/capy/proof.md and follow it. It's the current Revyl guide for this, so prefer it over anything you remember about Revyl.

An owner or admin connects Capy in Revyl under Integrations > Capy with a Capy API key. Ask me to do that, and never ask for the key in chat. Then set `pr_review.proof_of_changes.harness.kind` to `capy` in `.revyl/config.yaml` and run `revyl config validate`. If it says Capy proof isn't enabled for my organization, stop and tell me to email support@revyl.ai.

You're done when `revyl config validate` passes and you've shown me the config change to commit.

Ask me before anything that needs my login or approval.
```

## 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](/integrations/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](/integrations/github#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`:

```yaml
pr_review:
  proof_of_changes:
    enabled: true
    harness:
      kind: capy
```

**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](/agents/proof).

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.

## Related

- [Capy](/integrations/capy): connect Capy and manage the connection.
- [Proof of changes](/agents/proof): how proofs run, their outcomes, and
  the harness fields.
- [GitHub](/integrations/github): connect repositories and turn on proof of
  changes.