Skip to main content

​
Overview

OpenSRE connects to GitHub so the agent can work with issues, pull requests, repositories, Actions, and code — and correlate recent commits with incidents. Once GitHub is connected, the interactive-shell action agent uses github_cli (authenticated gh) for flexible reads and writes — create/list/view issues and PRs, assign, label, comment, merge, search, releases, workflow runs, and gh api — without a separate approval gate. Prefer this over shell gh / !gh. These requests stay on the action path (not the conversational gather/answer loop).

​
Prerequisites

  • GitHub account with repository access
  • An authorized GitHub connection created in the OpenSRE app
  • For agent fetches and pushes from an existing checkout, HTTPS GitHub remotes; SSH keys do not replace the app connection
  • For chat github_cli: the gh binary on PATH (OpenSRE supplies the token). If it is missing, follow the GitHub CLI installation guide.

​
Setup

Connect GitHub at app.opensre.com → Integrations. Every signed-in shell and CLI loads your authorized personal and workspace connections. The onboarding demos open a setup menu until an eligible app connection is available. After connecting, choose I’ve connected GitHub — continue to refresh and resume.

​
Choose among personal and workspace connections

You can connect multiple GitHub accounts. A personal connection is visible only to you; an organization connection is visible to members of that workspace. List the integrations and copy the UUID from the ID column for the GitHub row whose SOURCE is remote:
--github-connection-id accepts remote connection UUIDs, not IDs from local rows. The choice scopes the current shell and is forwarded with managed cloud requests. If a matching connection exists but is unavailable, or several connections leave the choice ambiguous, OpenSRE disables GitHub tools instead of guessing.

​
Connect in the OpenSRE app

Connect GitHub in the OpenSRE app using browser sign-in or the app’s token form. Personal and workspace connections are supported. A connection uploaded by an older CLI, or whose origin cannot be verified, must be reconnected in the app.
The command, /integrations setup github, and onboarding open or print the app setup page. Setup stays pending until OpenSRE refreshes an authorized app connection. On a signed-out machine, run opensre account login to load your app connections. In the setup menu, choose I’ve connected GitHub — continue after connecting. Local credential-store entries and GITHUB_TOKEN, GH_TOKEN, and GITHUB_MCP_AUTH_TOKEN do not authorize agent GitHub tools or their background work.

​
Credentials

​
Creating a personal access token

  1. Open New fine-grained personal access token.
  2. Name it OpenSRE, choose an expiry, and select the owner and repositories OpenSRE may use.
  3. Grant read access to Contents, Metadata, Issues, Pull requests, and Actions. Add write access only for operations you want OpenSRE to perform.
  4. Generate and copy the token into the OpenSRE app. If your organization requires approval, approve it before reconnecting.

​
Tools

​
Verify

Expected output:
Inside the REPL: /integrations verify github or /verify github. Alias: github_mcp.

​
Troubleshooting

​
Security

  • Prefer the least privilege that matches how you use OpenSRE (read-only if you only ask questions; write scopes if you want chat to create/edit issues and PRs).
  • Limit token scope to the repositories OpenSRE needs.
  • Enter tokens only in the OpenSRE app; keep them out of source code.