Devin

Hand an environment finding to Devin with a prompt you can inspect before the session starts.

Review the handoff

From an environment finding, open Review session prompt and select the Devin connection. Check the repository and exact commit, then read the prompt before choosing Start in Devin.

The allowed-repository list controls which findings can use the connection. It does not grant Devin access to a repository; that access must already exist at the vendor.

Keep the session attached to the finding

Proofline records the session’s status and links to Devin and any verified pull request. You can return to the original finding while inspecting the proposed change.

Vendor finished means the session has finished its work. Review and test the change before treating the finding as fixed. A new commit needs a fresh review before another session starts.

Connect Devin

An organization administrator supplies the Devin API key and organization ID, then selects the allowed repositories. People starting sessions need operational access and GitHub write access to the repository.

Set up cloud coding-agent sessions

Get started with GitHub