A Codex Features Request Thread

Hi OpenAI team, I want to suggest a Codex UX improvement for users who manage complex, long-running projects with many related chats. Right now, project chats appear to be organized mostly by recent activity or internal sorting logic. That is useful in some situations, but it does not always match the real structure of a project. Many projects are not flat lists of conversations. They have phases, dependencies, categories, and a natural order. For these cases, Codex should support manual drag-and-drop ordering of chats inside projects, preferably through an “Edit layout” or “Edit project” mode. Suggested feature: Inside a Codex project, users should be able to: * Drag and drop chats into a custom order. * Create visual sections. * Move chats between sections. * Mark one chat as the project index or home chat. * Keep important/index chats at the top of the project. * Collapse and expand sections. * Save manual order independent of recent activity. * Optionally switch between “Recent activity order” and “Manual project order.” Small generic example: Project Home * Project Index / Overview Planning * Product strategy * Requirements * Architecture Build * Backend * Frontend * Database * Authentication Operations * Testing * Deployment * Bug reports * Support In this example, the visual order matters. The user may want “Architecture” to stay near the top, even if “Bug reports” was the most recently active chat. Use case 1: Long-running software project A software project may have chats for planning, backend, frontend, database, authentication, testing, deployment, bugs, and roadmap. These chats should be grouped according to the project structure, not only sorted by the last time they were used. Use case 2: Operational business workflow A business workflow may have stages such as lead capture, quotation, contract, billing, production, delivery, and support. That order matters because it represents how the work actually happens. Use case 3: Avoiding artificial naming hacks Today, users may add prefixes like A, B, C, 01, 02, or P01 just to force chats into a readable order. This helps, but it should not be the only way to organize a project. The chat title should describe the chat clearly. The project layout should control visual order. Use case 4: Separating different types of work A project can contain different types of chats: * Planning chats * Technical implementation chats * Documentation chats * Bug or issue chats * Deployment chats * Support or operations chats * Meta/project-index chats Without manual ordering and sections, these different categories can become mixed together. Use case 5: Project index or home chat Every serious project should be able to have a project index or home chat. This chat could explain: * What each chat is for * Where new topics should go * Which chats are active * What the project structure is This index chat should stay at the top of the project, regardless of recent activity. Suggested UI behavior: Inside a project, Codex could offer: * Sort by recent activity * Sort alphabetically * Manual order * Edit layout In “Manual order,” the user’s custom arrangement would be preserved. In “Edit layout,” the user could drag chats, create sections, and choose which chat is the project home/index. Why this matters: Codex is becoming more than a single-task coding assistant. For many users, it is becoming a workspace where project context, execution, planning, and decisions live together. Manual project chat organization would make Codex stronger for: * Developers * Founders * Product teams * Operators * Consultants * Small businesses * Long-running technical projects * Multi-chat workflows This is not only a cosmetic improvement. It would help users organize work according to real project structure, not only according to recency. Thank you for considering this request.