GitHub

Give agents GitHub access that lands in review.

Select the repositories an agent can use, limit its branch patterns, keep pull requests in normal review, and grant merge separately.

GitHub authority in the product

Limit repository access and sensitive PR actions separately.

The Agent identity carries the repository and branch rules. Ask mode can then pause the exact pull request call before GitHub receives it.

Maintenance Agent identity with a GitHub pull request grant limited to a selected repository and agent branches
The GitHub grant names the repository and branch pattern available to this Agent identity.
Pending GitHub pull request approval showing the exact owner, repository, title, head branch, and base branch
The pull request write pauses with its exact arguments when the matching action uses Ask mode.

Integration shape

See where the agent runs, which credentials it receives, and what ExecWarden records.

Agent loop

Any supported agent loop can request GitHub work through ExecWarden.

Tools

GitHub is the clearest first system to connect.

Credentials

The GitHub credential can stay in ExecWarden instead of being copied into the agent environment.

Repository controls

Repository allowlists, branch patterns, PR creation, approvals, and separate merge authority limit what the agent can change.

ExecWarden evidence

The activity log can record the caller, grant, GitHub action, approval, and provider result.

First setup

Connect GitHub, grant the selected repositories and branch pattern, then run a branch-first task.

Why GitHub first

Separate repository access, review branches, and merge authority.

A branch and PR make the agent's output inspectable without giving it direct main-branch authority.

Selected repositories

Grant the repositories this task needs.

A repo allowlist is easier to reason about than a user-level token copied into the agent environment, and it can be as narrow or broad as the task requires.

Branch pattern

Let the agent push review branches.

Branch-shaped output keeps normal code review, checks, comments, and merge decisions intact.

Merge access

Keep merge as a separate grant.

Merge authority should be absent or approval-gated unless the workflow has earned that trust.

Examples

GitHub tasks that end in normal review.

1Dependency update with tests and a PR.
2Failed CI investigation that pushes a focused branch.
3Activity record linked to a GitHub provider result.

Get started during beta

Start with one concrete task and a clear access plan.

Use the app during beta, or open the docs and choose the first agent task you want to control.

Connect GitHubRead GitHub quickstart