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

**URL:** <https://community.openai.com/t/feature-request-per-project-github-repository-and-file-folder-scoping/1390758>\
**Category:** Feature requests\
**Created:** [August 16, 2026, 6:17pm UTC](https://community.openai.com/t/feature-request-per-project-github-repository-and-file-folder-scoping/1390758 "2026-08-16T18:17:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sllion](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@sllion](https://community.openai.com/u/sllion)\
**Post date:** [August 16, 2026, 6:17pm UTC](https://community.openai.com/t/feature-request-per-project-github-repository-and-file-folder-scoping/1390758/1 "2026-08-16T18:17:47Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![OpenAI\_Support](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/openai_support/32/561845_2.png) [@OpenAI\_Support](https://community.openai.com/u/OpenAI_Support)\
**Post date:** [September 7, 2026, 12:27pm UTC](https://community.openai.com/t/feature-request-per-project-github-repository-and-file-folder-scoping/1390758/2 "2026-09-07T12:27:46Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Prashant\_Pardesi](https://avatars.discourse-cdn.com/v4/letter/p/f9ae1b/32.png) [@Prashant\_Pardesi](https://community.openai.com/u/Prashant_Pardesi)\
**Post date:** [September 7, 2026, 12:28pm UTC](https://community.openai.com/t/feature-request-per-project-github-repository-and-file-folder-scoping/1390758/3 "2026-09-07T12:28:48Z")

</div>