A Codex Features Request Thread

Thanks for the feedback. Here is the core use case in plain form: I have multiple Codex chats inside the same project, each representing a different part of the workflow: planning, architecture, backend, frontend, testing, deployment, bugs, and support. The problem is that the chat list appears to be organized mainly by recent activity, but real projects often have a logical order that is different from recency. For example, I may want: 1. Project Index / Overview 2. Planning 3. Architecture 4. Backend 5. Frontend 6. Testing 7. Deployment 8. Bugs / Support Even if “Bugs / Support” was the most recently active chat, I may still want it to stay lower in the project structure. Suggested fix: allow manual drag-and-drop ordering of chats inside a project, ideally with an edit mode and optional sections.