
Integration · Build & run
Your repos, issues and pull requests.
Ask what shipped, what is stuck and what is waiting on review. Brigham.ai reads GitHub and answers with links.
What it does
Status at a glance
Open pull requests, review waits and stale branches.
Issue triage
Summaries of what is open, by repo or label.
Context for changes
What a pull request changes and why, from its description and discussion.
Scopes and access
- Connects as
- Each person, their own account
- Access
- Read-only by default
- Reads
- Repositories, issues, branches, pull requests you can access
- Writes
- Comments and issue updates (separate grant)
- Needs approval
- Merging, pushing or changing repository settings
- Visibility
- Only repositories the connecting person can see
- Availability
- Available

Yours to connect, yours to revoke.
Each person connects their own accounts from the Connections page. Every connection can be revoked on its own, and every connection starts read-only. A write scope is a separate, explicit grant.
- Credentials are encrypted at rest and referenced by id. They never appear in model context, logs or tool results.
- Each agent gets its own connection grants.
- Tool results from outside sources are untrusted data. They cannot approve anything.
Ask it
- ›“Which pull requests have waited on review for more than two days?”
- ›“What merged to main this week?”
- ›“Summarize the open issues labeled bug.”
- ›“What changed in the billing branch?”
Questions, answered.
Can Brigham.ai merge code?
Not without approval, and not unless you grant write access.
Is issue text trusted?
No. Issues and comments are untrusted data and cannot approve an action.
