Codex Desktop: add project-level topics / grouped threads in the sidebar
What are you asking for?
Please consider adding project-level topics or grouped threads to Codex Desktop, similar to Telegram topics.
Problem
The current left sidebar model feels like:
Project = workspace / working directory
This works for small repositories, but it becomes awkward for monorepos or long-lived engineering workspaces with multiple subprojects and recurring work streams.
For example, a single workspace may contain:
- frontend
- backend
- Electron app
- shared packages
- code review
- release / packaging
- debugging
- experiments
- individual feature tickets
If I create a separate Codex project for every subproject, the sidebar becomes noisy and fragmented. If I only create one root project, all threads are mixed together and hard to organize over time.
Suggested design
A better model would be:
- Project / Workspace as the top-level sidebar item
- Topics / Sections inside each project
- Threads grouped under topics
- Optional default working directory per topic
- Topic-level pinning, archiving, collapsing, and search
- Ability to move existing threads between topics
- Inheritance from the project's AGENTS.md, with optional topic-specific guidance
Example:
Codex Project: wiz-electron
- frontend
- backend
- review
- release
- DVP rules
- experiments
Why this matters
This would make Codex Desktop much more usable for monorepos, multi-service systems, and long-running engineering projects. It would reduce sidebar clutter while keeping related work under the same project context.
In my daily workflow, I often work with a root engineering workspace that contains multiple subprojects. I want to keep them under one Codex project, but separate long-running threads by topic.
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Adding a related request from a Codex Desktop Windows workflow.
In addition to project-level topics/grouped threads, it would be very useful to have user-created folders in the left sidebar that are not necessarily tied to a filesystem folder or project root.
Desired behavior:
This would help when Codex is used across many projects and long-running workstreams. The current project/workspace grouping is useful, but users also need a personal organization layer for their own working structure, for example clients, product areas, active/paused work, reviews, experiments, or administrative folders.
This is not a cosmetic request. It is a basic information-architecture requirement, and it is becoming a serious usability blocker.
A flat list of projects and chats does not scale. Once someone has more than a handful of ongoing workstreams, the sidebar turns into an unmanageable pile of similarly weighted items. The current workarounds — pinning, renaming, archiving, and searching — do not provide an actual structure:
This is particularly damaging for beginners and for anyone using Codex as a long-term workspace. They are expected to remember where everything is in a flat, activity-driven list instead of being given a clear hierarchy. That makes the product feel unfinished and needlessly chaotic.
Please treat this as a high-priority usability issue. At minimum, Codex needs:
The fact that #32124 had to be closed as a duplicate of this issue makes the demand clearer, not less urgent: users are independently asking for the same missing capability. A productivity app with this ambition should not force people into an ever-growing flat sidebar.
Important clarification: the requested hierarchy must not stop at “topics inside one project.”
Codex also needs a separate user-defined organization tree above projects. Projects themselves should be items that can live anywhere in that tree, alongside folders or organizational nodes. This hierarchy must not be limited to filesystem containment or local repository structure.
For example:
Each level should be independently expandable/collapsible, and the depth should be effectively unlimited. A user may want only five to ten top-level nodes, then navigate downward through departments, work areas, projects, subprojects, and finally chats/threads.
The required model is therefore:
This is a personal information architecture for the Codex workspace, not merely a reflection of disk folders. It should support arbitrary nesting, drag-and-drop relocation, stable ordering, collapse/expand at every level, and persistence across restarts. Without this top-level organizational layer, even “nested projects” still leave users with a flat and chaotic project list.
Please explicitly include this broader hierarchy in the scope of this issue rather than treating it as only project-level thread grouping.