Agent loop
Any supported agent loop can request GitHub work through ExecWarden.
GitHub authority in the product
Scope repository access and sensitive PR actions separately.
The Agent identity carries the repository and branch boundary. Ask mode can then pause the exact pull request call before GitHub receives it.
Integration shape
The setup, credentials, governed actions, and evidence should be obvious.
Tools
GitHub capabilities are the clearest first system to govern.
Credentials
The GitHub credential can stay in ExecWarden instead of being copied into the agent environment.
Governed actions
Repo allowlists, branch patterns, PR creation, approvals, and separate merge authority can define the boundary.
ExecWarden evidence
The activity log can record the caller, grant, GitHub action, approval, and provider result.
Start
Connect GitHub, grant the selected repositories and branch pattern, then run a branch-first task.
Why GitHub first
How this boundary works in practice.
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 boundary
Keep merge as a separate grant.
Merge authority should be absent or approval-gated unless the workflow has earned that trust.
Examples
Example tasks and outcomes.
Get started during beta
Start with one bounded task and one boundary to review.
Use the app during beta, or open the docs and choose the first agent task you want to govern.