Feature Request: Per-Project GitHub Repository and File/Folder Scoping

Allow each ChatGPT Project to attach selected GitHub repositories and explicitly choose which folders/files from each repository become Project context.

Today, GitHub access is available globally, but there is no way to define exactly which repositories, folders, or files belong to a specific ChatGPT Project.

Desired behavior

  • Select repositories independently for each ChatGPT Project

  • Select, include, or exclude folders and individual files

  • Show Project context capacity consumed by selected sources

  • Keep selected GitHub content synchronized with the repository

  • Show the branch and commit currently indexed

  • Allow manual refresh/re-index

  • Automatically exclude common generated directories such as node_modules, vendor, build, dist, etc.

  • Keep GitHub sources isolated to the Project they were added to

Claude Projects currently provide a similar workflow where a user selects a repository, chooses specific folders/files, and can see how much of the project context capacity those sources consume.

This would be especially useful for software projects with multiple repositories, where only a subset of each repository is relevant to a particular Project.

ChatGPT already has GitHub integration, but adding Project-level GitHub source management would improve context isolation, token efficiency, source relevance, and usability for multi-repository development workflows.

Thanks for the request for per-Project GitHub repository and file/folder controls, with branch and refresh options. Current GitHub access retrieves permitted content on demand: https://help.openai.com/en/articles/11145903. We'll share the more granular Project controls with the team. No timeline to share yet!