Codex app: support Projects with movable chats, shared memory, and shared uploaded files
Open 💬 7 comments Opened Mar 7, 2026 by its-DeFine
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
Add Projects to the Codex app, similar to ChatGPT Projects. A project should let users:
- create a named project container
- move existing chats into a project after the fact
- have chats inside the same project share project-scoped memory/context
- upload files once at the project level so all chats in that project can use them
- optionally define project-level instructions/context that apply across those chats
Why this matters
Right now, related Codex chats are isolated from each other. For multi-session work, users have to restate the same context, re-upload the same files, or keep everything in one long thread. That makes ongoing work harder to organize and increases repetition.
Proposed behavior
- New and existing chats can be assigned to a project.
- Moving a chat into a project preserves the thread while applying the project context for future turns.
- Files uploaded to a project become available to all chats within that project.
- Shared memory should be scoped to the project, not globally across all Codex chats.
- The model should clearly show when a chat is inside a project and which files/context are shared.
Related context
This is conceptually similar to ChatGPT Projects, where multiple chats can live under one project and share memory plus uploaded files. Bringing that model to Codex would make longer-running coding, research, and operations workflows much easier to manage.
Related but not identical issues:
Are you interested in implementing this feature?
No, I'm requesting the capability as a product feature.
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This resonates. Shared memory/files would help, but I suspect the deeper issue starts once a team uses multiple chats or agents inside the same project: context sharing alone doesn't solve handoff, role consistency, or workflow drift.
+1. Very painful to create a chat and then realize you can't add it to a project afterwards.
Yes please. So many times I start what I think is a quick little chat and it balloons into a 'project' and I want to just promote it to a real project.
Please add this feature as I'm currently facing the exact same dilemma.
Same here! please implement this soon!
Same. Same. I also want to be able to change a chat's "cwd" since they seem to get stuck associated with the starting directory. Sometimes I need to take a spike of work I created in a small chat as an experiment but then want to make it into a full fledged part of a project. I don't create them in the project to begin with because I create many of them as experiments and don't know if they will turn out or not. Many don't.