codex - 💡(How to fix) Fix Allow multiple logical projects in the same folder/repo

What variant of Codex are you using?

App

What feature would you like to see?

I would like Codex to support creating multiple logical projects for the same local folder or repository.

Right now, a Codex project appears to be primarily tied to a folder/repo path. That works well when each folder maps to one project, but many real workflows have several distinct initiatives inside the same repository or workspace.

For example, I may have one repo/folder that contains multiple areas of work:

• Marketing
• Development
• DevOps
• Documentation
• Customer-specific implementation
• Experiments or prototypes

These are all in the same folder/repo, but they should not necessarily share the same Codex project context, history, instructions, or thread list.

Requested behavior

Please add the ability to create multiple named Codex projects/profiles that point to the same folder/repo.

Example:

Repository/folder: ~/work/company-repo

Codex projects:
- Marketing
- Development
- DevOps
- Documentation

Each logical project should be able to share the same underlying folder/repo while keeping its own project-level organization.

Ideally, each project/profile could have its own:

• Name
• Thread/conversation history
• Project-specific instructions
• Pinned files or context
• Notes or memory
• Searchable project history
• Optional default working scope, such as a subdirectory, file group, or task area

Why this matters

This would make Codex much easier to use with real-world repositories where one repo contains several workstreams.

For example, in the same repo I may want to use Codex for:

• Writing and editing marketing content
• Implementing frontend/backend development tasks
• Reviewing deployment or infrastructure changes
• Maintaining documentation
• Planning future features

These tasks often need different context and different conversations. Mixing them all into one project makes it harder to find the right thread later and can cause unrelated context to leak into the wrong task.

The current workaround is to either:

1. Keep everything in one Codex project, which becomes cluttered over time.
2. Duplicate the repo/folder just to create separate Codex projects, which is wasteful and can create Git/branch confusion.
3. Use multiple folders or worktrees even when the actual desired workspace is the same repo.

A first-class “multiple projects per folder/repo” feature would avoid those workarounds.

Desired user experience

A possible flow:

1. User opens a folder/repo in Codex.
2. Codex shows existing logical projects for that folder, or allows creating a new one.
3. User creates a new project named “Marketing” or “Development”.
4. The project uses the same local folder/repo, but keeps its own Codex conversations and instructions.
5. When opening the same folder later, Codex asks which project/profile to use, or allows switching between them from the sidebar.

For example:

Open folder: ~/work/company-repo

Choose Codex project:
- Marketing
- Development
- DevOps
- Documentation
+ Create new project for this folder

Possible implementation ideas

Some possible approaches:

• Add a “Create another project for this folder” action.
• Store project identity separately from the folder path.
• Allow multiple project records to reference the same path.
• Add a project switcher when a folder has more than one Codex project.
• Allow optional per-project instructions, like:
  • “For Marketing, focus on copy, landing pages, analytics, and SEO.”
  • “For Development, focus on application code, tests, refactors, and architecture.”
  • “For DevOps, focus on deployment, infrastructure, CI/CD, and environment configuration.”

Expected benefit

This would make Codex more useful for monorepos, product teams, agencies, and anyone who uses one repository for multiple areas of work.

It would also improve long-running project organization by keeping unrelated threads separate without requiring users to create duplicate folders or artificial repo structures.

Additional information

This request is different from multi-root or multi-repo support.

This feature is specifically about allowing multiple logical Codex projects to intentionally share the same folder/repo while keeping separate project identities, instructions, histories, and thread organization.

In other words, this is not primarily asking for one Codex project to span multiple folders or repositories. It is asking for one folder/repo to support multiple Codex projects/profiles.