Reference · Cognition · updated 27 September 2026
The only one that lets an admin choose who the author is. Here is what its public documentation says about authentication, commit attribution, the sandbox it runs in, how you hand it work, and the limits you will hit.
| Auth | A managed GitHub App (devin-ai-integration), with a fine-grained personal access token path for GitHub Enterprise. Permissions are shared org-wide. |
| Attribution | Admin-configurable: open PRs as Devin, as the user, or user-only, with separate commit-attribution modes. Signed commits require a dedicated bot GitHub account with its own GPG key. |
| Sandbox | A Cognition-hosted VM. The docs do not detail isolation or network policy. |
| Task intake | /devin <prompt> or /devin review as the first line of a comment on an open PR. The commenter needs write access. Devin cannot create repositories. |
| Limits | Works only on open PRs from comments; org-wide permission scope rather than per-task. |
Every cloud agent in this series invents its own identity and attribution model, because the host gives them nothing to stand on. The consequences are the same across vendors: agents share a person's token or an org-wide app installation, so a fleet hits secondary rate limits as one user; attribution lives in free-text trailers the host never reads; and rules like "a human must approve changes under this path" are left to the agent to enforce on itself.
Paste this to your coding agent. A human approves one code on github.com; the agent does the rest.
Set up githug for owner/repo: run `curl -fsSL https://githug.ai/install | sh`, then `hug init --repo owner/repo --json`. Show me any code or link it prints and wait for it to finish.
Quickstart · Set it up yourself · free during the beta