A Codex Features Request Thread

I use Codex as a long-term operational workspace with many project-specific chats. Some chats act as index/master maps for the entire workflow. Recently, I accidentally archived a critical pinned “work map” chat, which disrupted navigation across my Codex project. I’m requesting two UX improvements: 1. Manual drag-and-drop ordering of chats inside projects, preferably in an edit mode. Hi OpenAI team, I want to suggest a Codex UX improvement based on a real workflow issue I experienced. I am using Codex as a long-term operational workspace, not only as a coding assistant. In this kind of workflow, some chats become structurally important. They are not just normal conversations. They become project maps, index chats, decision hubs, routing chats, or the main place where a user organizes many related Codex threads. Recently, I accidentally archived a pinned chat that acted as my main Codex work map. That chat contained the structure of my workspace: which project chats existed, what each one was for, how they were named, which chats were pinned, and where new topics should go. When that chat was archived, it felt like my main navigation system disappeared. My request is simple: Codex should show a confirmation dialog before archiving pinned, index, or project-critical chats. Suggested behavior: If a user tries to archive a pinned chat, Codex should ask for confirmation. Example: “You are about to archive a pinned chat: ‘Mapa de trabajo - Codex / Proyectos y chats.’ This chat may be important for your project navigation. Are you sure you want to archive it?” Suggested buttons: * Cancel * Archive chat A second useful layer would be an undo toast after archiving: “Chat archived. Undo.” This would protect users from accidental clicks, trackpad mistakes, or fast menu actions. Cases where Codex should show confirmation: * The chat is pinned. * The chat belongs to a project. * The chat has recent activity. * The chat was used as the source for creating other threads. * The chat title includes words like Index, Map, Master, Overview, Project, Architecture, or similar. * The user manually marks the chat as important or protected. Use case 1: Pinned chat as workspace map A user may have one pinned chat that works as the central map for a large project. It explains what each chat is for, which topics belong where, and how the project is organized. If this chat is archived accidentally, the user does not just lose a conversation from the sidebar. They lose the main navigation point for the entire workspace. Use case 2: Chat as project router A project can include many related chats, for example: * Website * WhatsApp * Contracts * Quotations * Billing * Installation * Documentation * GitHub * Product decisions An index chat helps decide where new work should go. If it disappears, the user may start creating duplicate chats, mixing topics, or losing confidence in the structure. Use case 3: Long-running professional workflows For long-running projects, some chats become durable project assets. They hold important context, decisions, naming conventions, workflow rules, and links between tasks. In these cases, archiving a chat is not a minor UI action. It changes the visibility of an important workspace asset. Use case 4: Business and non-technical users Codex is useful not only for developers. Founders, operators, consultants, and small teams can use it to organize and build business systems. For these users, a chat can function like an operational control point. Accidentally archiving that chat can be confusing and disruptive. Use case 5: Preventing accidental destructive actions Archiving may be reversible, but in practice it can feel like a chat disappeared, especially if the user does not know how to recover it. A confirmation dialog would prevent accidental loss of visibility for important chats without making normal chat cleanup difficult. Suggested extra feature: Protected chats Codex could also allow users to mark a chat as protected or critical. For protected chats: * Archiving requires confirmation. * Deleting requires stronger confirmation. * The chat remains visually marked as important. * The chat can optionally stay at the top of the project. Why this matters: As Codex becomes more useful for complex, long-term work, chats are no longer always disposable. Some chats become maps, indexes, planning surfaces, and coordination hubs. Protecting those chats would make Codex feel safer and more reliable as a professional workspace. This improvement would help users avoid accidental disruption, especially when they are managing multiple projects, pinned chats, and long-running workflows. Thank you for considering this request. I would be happy to provide more concrete examples or screenshots from my workflow if helpful.