codex - 💡(How to fix) Fix Allow Chats to be moved into, out of, and between Projects

What variant of Codex are you using?

App

What feature would you like to see?

Summary

Please add support for re-homing existing Codex chats that live under Chats into a selected project under Projects, and more generally allow chats to be moved:

• from Chats into Projects
• out of Projects back into Chats
• between one Project and another

Why this matters

Codex already presents Projects as containers that can hold chats. In the desktop UI, projects appear with a chat count area beneath them, which makes it natural to expect chats to be organizable within those projects.

Because of that UI model, it is confusing and limiting that a chat started under Chats cannot later be associated with a project, even when the conversation clearly becomes project-specific.

This is a real workflow blocker, not just a cosmetic preference.

Example workflow that currently breaks down

1. Start a general-purpose Codex chat under Chats
2. Use it for research, planning, debugging, or product discussion
3. Realize the conversation belongs with a specific codebase or project
4. Try to move it into that project for organization and future retrieval
5. Discover there is no supported way to do so

At that point, the user is forced to leave relevant project context stranded under Chats, which fragments work history unnecessarily.

Expected behavior

Codex should provide a way to move or assign an existing chat to a project after creation.

Possible UX options:

• Move to Project
• Add to Project
• drag-and-drop from Chats into a Project
• project reassignment from a chat overflow menu

It should also be possible to:

• remove a chat from a project
• move a chat from one project to another

Why this is consistent with Codex

This would make Codex behave more like the broader ChatGPT Projects model and more like normal IDE/workspace organization patterns.

Users often begin with a loose conversation and only later determine the correct project affiliation. The system should support that natural progression instead of requiring perfect categorization at chat creation time.

Additional context

I also submitted in-product Codex feedback for this request.

Feedback thread ID:

019e1cb8-45e7-7bc0-9f68-fd7c46a5c2e0

Additional information

Codex feedback thread ID: 019e1cb8-45e7-7bc0-9f68-fd7c46a5c2e0