You can now connect your GitHub repositories to deep research and ask questions based on your own code.
đĄ Availability: ChatGPT deep research with GitHub is available globally to Plus, Pro, and Team users. Enterprise user access will be announced at a later date.
â ď¸ Note: This feature is currently in beta. Please note that connected apps like GitHub are third-party services and subject to their own terms and conditions.
How do I connect GitHub to ChatGPT deep research?
You can connect GitHub to ChatGPT by selecting Deep research in the composer, pressing the down arrow, and selecting GitHub. From there, youâll be directed to GitHub to install and authorize the ChatGPT connector, and then select the repositories ChatGPT can access
You can also enter this connection flow by going to ChatGPT Settings, selecting Connected apps, navigating to Connectors and selecting Connect next to GitHub. If you later want to change which repositories the connector can access, click the Gear icon next to GitHub in settings to navigate to GitHubâs connector configuration page.
Why donât I see some of my repositories after connecting ChatGPT to GitHub?
Generally thereâs a ~5 minute delay before your repositories will start showing up in the deep research GitHub connector.
Additional reasons why you may not see a repository yet:
Private or newly created repositories: If your repository is private or was created after initially connecting to GitHub, it may not appear immediately in ChatGPT. Please visit this link or tap on the Gear icon in the Settings page for Github in ChatGPT to configure access to the desired repositories.
âRepository requires GitHub admin approval: Your repository may be blocked by your GitHub admin from being connected to ChatGPT. Please visit this link or tap on the Gear icon in the Settings page for Github in ChatGPT. From here, you can âRequestâ access to repositories that can be approved by your IT administrator.
âRepositories not indexed by GitHub: Due to GitHubâs search indexing behavior, the repository may not be in GitHubâs index, and therefore isnât visible to the ChatGPT connector when searching. You can manually trigger indexing by going to GitHub and performing a search for the repository using this format:
repo:{username/repo_name} import(e.g., repo:openai/codex import). Note that the index may take ~5-10 minutes before it becomes available to the connector.
How does deep research work with GitHub?
When you connect GitHub to deep research, ChatGPT can pull live data from your repositoriesâcode, README files, and other docsâand reason over it in real time. Just connect, ask a question, and deep research will read, analyze, and cite the relevant snippets straight from your GitHub content.
What does ChatGPT share with Github when I connect GitHub to deep research?
ChatGPT forms search queries from your prompts to find relevant information in your connected GitHub repositories and sends these queries to GitHub. For example, if you ask, âCan you show me where I handled file uploads in the backend?â ChatGPT might search your GitHub repositories using a query like âfile upload handler backend.â If needed, it may do a few different searches to find the most relevant code or files.
Will OpenAI use content from GitHub to train its models?
By default, content sent by customers using business offeringsâsuch as ChatGPT Team, Enterprise, Edu, and our APIâis not used to improve our models. Please see our Enterprise Privacy page for information on how we use business data.
When you use our services for individuals such as ChatGPT Free, Plus, and Pro, we may use your content to train our models if your âImprove the model for everyoneâ setting is on. You can read more about how your data is stored and used in this article in our help center.
How can GitHub admins approve the ChatGPT connector?
GitHub admins can follow these instructions to approve OAuth apps, such as the ChatGPT connector, for their organization.
How do I search for individual files in a repository?
You can only search for the name of your GitHub repositories. Searching for specific file names is not supported.