Integrations
Capy
Let Capy prove pull requests and take on work from Atlas
Revyl works with Capy in two ways. Both start threads in your Capy projects, and both use the Capy connection you set up below.
| Proof via Capy | Capy cloud agents | |
|---|---|---|
| Typical use | Prove that a pull request does what it claims | Hand a screen from Atlas to an agent to fix, investigate, or check |
| Starts from | A pull request | A screen in your app's Atlas |
| Reports back | On the pull request | In Capy, and in the Atlas comment thread it started from |
Capy is in alpha. To add it to your organization, email support@revyl.ai.
Connect Capy
1. Create a Capy API key
In Capy, open Settings → API and create a key for Revyl to use.
2. Connect Revyl to Capy
Go to Integrations > Capy and click Connect Capy. Paste the key and click Continue. Revyl lists the Capy projects the key can see, with the repositories each one checks out. Select the projects Revyl may start threads in, then click Connect Capy. Revyl stores the key encrypted and shows only a hint of it afterwards.
Owners and admins connect Capy for the organization. This key is the organization default.
Managing the integration
- Check connection: verify the saved key against Capy.
- Edit projects: change which Capy projects Revyl may start threads in.
- Reconnect: when the connection shows Needs reconnect, Capy rejected the saved key. Paste a new one.
- Disconnect: remove the organization's key from Revyl. Projects with their own proof keys are unaffected.
Related
- Proof via Capy: let Capy prove your pull requests.
- Cloud agents: spawn Capy agents from Atlas screens.
- MCP setup: connect your own coding agent to Revyl.