Summary
The July 23, 2026 multi-folder local-project release improves how users organize existing local work, but it does not let Pro subscribers use the Chat/Pro models they pay for within those projects.
In the unified ChatGPT/Codex experience on macOS, a local project can use Work chats with access to its local folder, but it cannot use Chat with the ChatGPT/Pro model surface. The desktop app states: “Local projects don't support Chat.”
Choosing Continue as task preserves the local-project/file workflow, but switches away from the Chat/Pro model surface. Staying in Chat preserves the selected Chat model, but removes the local project context and access to its current files.
The same practical split also affects browser-based Chat: Chat can provide the selected model surface, but it does not retain the local-project folder and Work context.
Why this matters for Pro subscribers
Many Pro subscribers pay specifically to use certain Chat/Pro models for high-quality reasoning and review. That model choice should remain available when reviewing or continuing work already created inside an existing local project.
Instead, the current product forces a choice between:
- Chat/Pro reasoning without the project’s local files and Work history; or
- Local-file Work access without the Chat/Pro reasoning surface.
Selecting Continue as task removes the model surface the user intentionally chose at the point it is most needed. The product should not require Pro subscribers to choose between their paid Chat model and their current project context.
New project-folder functionality does not bridge the gap
The July 23, 2026 ChatGPT desktop release (version 26.715) added multi-folder local projects. A local project can attach related folders and select a primary folder; the primary folder controls where new Work chats start and where Git operations and project-instruction discovery run.
This is useful for organizing which local files a Work chat uses. However, changing the primary folder or adding another local folder does not make the local project available in Chat. The project remains a Work-only local project, and Chat still shows the same limitation. The new folder-management capability therefore does not solve the need to use a Chat/Pro model with the current local project context.
Steps to reproduce on macOS
- Add a local folder as a project in the macOS desktop app.
- Optionally add more local folders and make one primary.
- Start a new chat from that local project.
- Switch to Chat, or select a ChatGPT/Pro model.
- Observe the message: “Local projects don't support Chat.”
- Select Continue as task and observe that the session becomes a Work task instead of remaining a Chat/Pro conversation.
Expected behavior
A local project should be able to contain both Work and Chat conversations. Chat should support an explicit, user-controlled way to review selected local files and retain relevant project context without copying, moving, or converting the project.
This does not require automatic sharing of local files or terminal access. The user should explicitly select what local artifacts or project context are available to Chat.
Environment
- macOS desktop app, version 26.715
- Chat in the desktop app and browser
- Observed after the July 23, 2026 multi-folder local-project release
Summary
The July 23, 2026 multi-folder local-project release improves how users organize existing local work, but it does not let Pro subscribers use the Chat/Pro models they pay for within those projects.
In the unified ChatGPT/Codex experience on macOS, a local project can use Work chats with access to its local folder, but it cannot use Chat with the ChatGPT/Pro model surface. The desktop app states: “Local projects don't support Chat.”
Choosing Continue as task preserves the local-project/file workflow, but switches away from the Chat/Pro model surface. Staying in Chat preserves the selected Chat model, but removes the local project context and access to its current files.
The same practical split also affects browser-based Chat: Chat can provide the selected model surface, but it does not retain the local-project folder and Work context.
Why this matters for Pro subscribers
Many Pro subscribers pay specifically to use certain Chat/Pro models for high-quality reasoning and review. That model choice should remain available when reviewing or continuing work already created inside an existing local project.
Instead, the current product forces a choice between:
Selecting Continue as task removes the model surface the user intentionally chose at the point it is most needed. The product should not require Pro subscribers to choose between their paid Chat model and their current project context.
New project-folder functionality does not bridge the gap
The July 23, 2026 ChatGPT desktop release (version 26.715) added multi-folder local projects. A local project can attach related folders and select a primary folder; the primary folder controls where new Work chats start and where Git operations and project-instruction discovery run.
This is useful for organizing which local files a Work chat uses. However, changing the primary folder or adding another local folder does not make the local project available in Chat. The project remains a Work-only local project, and Chat still shows the same limitation. The new folder-management capability therefore does not solve the need to use a Chat/Pro model with the current local project context.
Steps to reproduce on macOS
Expected behavior
A local project should be able to contain both Work and Chat conversations. Chat should support an explicit, user-controlled way to review selected local files and retain relevant project context without copying, moving, or converting the project.
This does not require automatic sharing of local files or terminal access. The user should explicitly select what local artifacts or project context are available to Chat.
Environment