> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub

The **GitHub** connector integrates Tess with GitHub for code collaboration. Once connected, the AI can inspect repositories, summarize pull requests and issues, and support engineering workflows inside chats and agents.

GitHub is part of the Tess [Connectors](/en/connectors) ecosystem and uses **OAuth** authentication for Apps connectors.

## Prerequisites

<Info>
  * A GitHub account with access to the repositories you want to use.
  * Permission to authorize the GitHub OAuth app for those repos/orgs.
</Info>

## How to connect

<Tip>
  On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
</Tip>

<Steps>
  <Step title="Open the Connectors panel">
    In chat, click the **+** next to the message box and select **Connectors**. You can also manage connectors while editing an agent in Agent Studio.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/github/01-connect-panel.png" alt="PRINT: (Connectors panel with GitHub highlighted and the Connect button visible)" />
    </Frame>
  </Step>

  <Step title="Find GitHub and click Connect">
    Under **Apps**, locate **GitHub** and click **Connect** to start authentication.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/github/02-oauth-consent.png" alt="PRINT: (Provider authorization / consent screen for GitHub)" />
    </Frame>
  </Step>

  <Step title="Authorize access">
    Sign in with the account you want to use and review the requested permissions before confirming.
  </Step>

  <Step title="Confirm it is active">
    Back in Tess, **GitHub** should appear under **Connected**, ready for chats and agents.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/github/03-connected.png" alt="PRINT: (Tess callback or Connectors list showing GitHub as Connected with a success state)" />
    </Frame>
  </Step>
</Steps>

## What you can do

* **List and inspect repositories**, branches, and recent activity
* **Review pull requests** — summarize changes, comments, and status
* **Work with issues** — search, create, update, and triage
* **Support release and CI context** when the account can see checks and workflows
* **Help product and engineering teams** keep technical context in one place

## Example prompts

> 1. List the most recent pull requests in the project and summarize the purpose of each one.
> 2. Find issues related to the connectors integration and organize them by priority.
> 3. Summarize what changed in the latest open PRs and call out risks.
> 4. Create an issue titled 'Docs gap on Connectors' with a short description and label it documentation.

## Best practices

* Name the owner/repo when you have access to many repositories.
* Ask for a summary before requesting code-changing actions.
* In agents, clarify whether GitHub is for status, triage, or drafting changes.

## Troubleshooting

<AccordionGroup>
  <Accordion title="OAuth denied or missing repos" icon="circle-question">
    Re-authorize with an account that can access the organization/repos, and approve org access if GitHub asks.
  </Accordion>

  <Accordion title="401 / connection dropped" icon="circle-question">
    Reconnect GitHub in Connectors after password, SSO, or token revocation changes.
  </Accordion>

  <Accordion title="Private repo not found" icon="circle-question">
    Confirm the connected account has permission on that repository.
  </Accordion>
</AccordionGroup>

<Note>
  Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.

  Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.
</Note>