GitHub

Connect GitHub to investigate code and manage development work from Agent Mode

Connect GitHub to let Agent Mode correlate production behavior with code, issues, pull requests, and Actions runs—and take follow-up actions without losing investigation context.

What You Can Do

Read and investigate

Find recent pull requests that changed the checkout service, inspect their diffs, and identify changes that could explain this latency regression.

Summarize the failing GitHub Actions run for this repository and check whether an open issue or pull request already tracks it.

Take action

Create a GitHub issue for this monitor problem with the impact, relevant telemetry, suspected code path, and a link to the groundcover investigation.

Add the confirmed root cause and reproduction steps to the existing issue, then draft a pull request with the fix for me to review.

The available repositories and actions depend on the connected account, token scopes, and tool restrictions.

Setup with a Personal Access Token

GitHub uses personal access tokens by default.

1. A workspace admin goes to Integrations → Connectors → Org Connectors, selects GitHub, and enables it.

2. The admin enters a GitHub personal access token to discover the available tools and reviews the tool restrictions.

3. Each user goes to Integrations → Connectors → My Connections, selects GitHub, and clicks Connect.

4. Enter a personal access token with access to the repositories and operations Agent Mode should use.

Optional: Switch to OAuth

A workspace admin can switch GitHub to OAuth after creating a GitHub OAuth App:

1. Open GitHub Developer settings, select OAuth Apps, and click New OAuth App.

2. Complete the form:

   • Application name: Any recognizable name, such as groundcover.

   • Homepage URL: Any valid URL, such as your top-level groundcover URL.

   • Application description: Optional.

   • Authorization callback URL: Your top-level groundcover URL, usually https://app.groundcover.com/.

3. Leave Enable Device Flow disabled and click Register application.

4. Copy the Client ID and generate a Client Secret.

5. In groundcover, open Integrations → Connectors → Org Connectors → GitHub and click Edit under General Information.

6. Set Authentication Method to OAuth, enter the Client ID and Client Secret, and click Save.

7. Click Connect under Tool Restrictions and complete authorization.

Use the top-level groundcover URL for the Authorization callback URL and leave Device Flow disabled.

groundcover includes the tenant UUID and backend ID in the OAuth state parameter. The callback validates this state and routes the authorization response to the correct groundcover environment.

New personal connections use OAuth after the switch; existing token connections continue to work. Switching back to Token removes the stored OAuth client, but existing OAuth connections continue until they expire and must then reconnect with a token.

Agent Mode acts with the connected user's GitHub permissions, subject to groundcover's tool restrictions. Write actions may require approval.