Cotool + GitHub
Connect GitHub to Cotool so agents read code, commits, and blame, open pull requests, sync agents as code, and ingest GitHub audit logs, with read-only option.
The short answer
The GitHub integration connects Cotool to repositories through a GitHub App. Agents read files, commits, blame, pull requests, and branch rules, can open and update pull requests when their workflow needs to change code, and can sync response agents and skills as code. GitHub audit logs can also be ingested into Cotool.[1][2]
How it connects: Connect with the Cotool-managed GitHub App, with a GitHub App your organization registers and owns, or both. With your own App, GitHub enforces the permissions you chose on every request Cotool makes.[1][6]
What Cotool uses from GitHub
Response actions
These change state in GitHub, so they are the steps teams usually gate behind approval.
Detections, hunts, and triage
Setup and permissions
Install the GitHub App on an organization and pick all or selected repositories. For your own App, create it in GitHub, then give Cotool its App ID, client ID, client secret, and private key.[1]
| Permission | Access | Why |
|---|---|---|
| Contents: ReadRead files, commits, blame, branch rules, and repository metadata.[1][6] | Read | Read files, commits, blame, branch rules, and repository metadata.[1][6] |
| Pull requests: ReadRead and list pull requests.[1][6] | Read | Read and list pull requests.[1][6] |
| Organization members: ReadRequired on your own App so setup can verify the installer is an organization owner.[1][6] | Read | Required on your own App so setup can verify the installer is an organization owner.[1][6] |
| Contents and Pull requests: Read and writeCommit to branches and open, update, or close pull requests. Leave at Read for a read-only App.[1][6] | Write | Commit to branches and open, update, or close pull requests. Leave at Read for a read-only App.[1][6] |
| Workflows: Read and writeCreate or update GitHub Actions workflow files.[1][6] | Write | Create or update GitHub Actions workflow files.[1][6] |
How Cotool works with GitHub
- A read-only App with Contents: Read, Pull requests: Read, and Organization members: Read lets agents investigate while GitHub itself refuses every write.[1]
- One Cotool organization can connect several GitHub organizations and route each repository to either the managed App or your own, with conflict detection.[1][2]
FAQ
- Can I give Cotool read-only GitHub access?
- Yes. Register your own GitHub App with read permissions only. Cotool's docs describe it as the most common reason to bring your own App.[1]
- What happens when I change my App's permissions?
- GitHub asks an organization owner to approve the new permissions for each installation. Cotool picks them up on its next request without a reconnect.[1]
Sources
- GitHub integration (Cotool docs) · accessed November 16, 2026
- Changelog (Cotool docs) · accessed November 16, 2026
- Response agents as code (Cotool docs) · accessed November 16, 2026
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Threat hunting (Cotool Hunt) · accessed November 16, 2026
- Choosing permissions for a GitHub App (GitHub Docs) · accessed November 16, 2026
- Managing private keys for GitHub Apps (GitHub Docs) · accessed November 16, 2026
- Reviewing the audit log for your organization (GitHub Docs) · accessed November 16, 2026

