What the agent can do
Read & write code
Clone repositories, make changes, and push commits.
Open pull requests
Propose changes as PRs for your team to review.
Manage issues
Create, comment on, and update issues.
Run workflows
Work with Actions, checks, and statuses.
Example agent tasks
Its own identity
The connection gives the agent a dedicated bot identity on GitHub, with its own name on commits and pull requests. You can see at a glance what the agent did versus what a human did, and reviews stay clean. It’s the agent’s installation, scoped to the repositories you grant it.Connecting
1
Authorize GitHub for the agent
From the agent’s connections, choose GitHub and install it on the org or the specific repositories you want it to access.
2
Pick the repositories
Grant access to all repos or only the ones the agent should touch.
3
The agent gets to work
It can now clone, commit, push, and open PRs against the repositories you granted, all under its own identity.
If you’re not an org owner
Connecting GitHub for an agent creates a dedicated GitHub App. When you connect it to an organization, GitHub only lets an owner (or an App Manager) create that app, so how you finish the install depends on your role.You’re a GitHub App Manager
GitHub’s membership API reports only owners, so if you hold the App Manager role rather than full ownership, the connect screen first shows your org as needing an owner. Choose I’m an App Manager and the org unlocks: you create the app yourself, and an org owner approves it afterward (the standard GitHub App approval, the same as any App Manager creating an app). Skydive remembers this, so next time your org is unlocked from the start.You’re neither an owner nor an App Manager
Skydive hands off instead of hitting a dead end: copy the link from the connect screen and send it to an owner of your org. They open it, sign in to Skydive, and complete the GitHub install under their own identity. When they’re done, the agent gets the same “GitHub connected” confirmation and can start working against the granted repositories.1
Start the connection
Begin connecting GitHub for the agent and pick your organization. If GitHub doesn’t already list you as an owner, you’ll see both the App Manager option and a link to copy for an admin.
2
Send the link to an org owner
Copy it and pass it to someone who owns the org. The link explains which agent it’s for and why access was requested.
3
The owner completes the install
They sign in to Skydive, continue to GitHub, and install the app on the org. The agent is notified and ready to go.
Scoped access
You control exactly which repositories the agent can reach and what it can do. Grant narrowly when you want a tight blast radius, or broadly for an agent that works across many repos. As with every connection, the underlying token is handled securely and never exposed to the model. See Permissioning.How credentials stay safe
The proxy model that keeps tokens out of the agent’s reach.