You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Codex Desktop: add project icons and show them next to pinned thread names #25448
Please add support for project icons in Codex Desktop, and use those icons consistently in places where project context matters.
Suggested behavior:
Allow each project/workspace to have an icon.
Show the project icon next to the project name in the sidebar.
Show the project icon before thread names in the pinned section, so pinned threads from different projects are easier to distinguish.
Fall back to the default project/folder icon when no custom icon is set.
Why this matters
Codex projects are mostly identified by text today. When working across several projects, especially with similar names or many pinned threads, it is easy to lose track of which workspace a thread belongs to.
Project icons would provide a fast visual cue and reduce the chance of opening or prompting in the wrong project. This is especially useful in the pinned section, where threads from multiple projects can appear together without enough project context.
Adding a specific use case to this request: please let people upload the actual logo for a local Codex project.
I use Codex across several businesses and client workspaces. In the Projects view, identical folder markers slow recognition. A project logo would let me spot the right workspace immediately and help prevent prompts from landing in the wrong project.
A useful implementation could accept SVG or PNG files, fit the image inside the existing project marker, and display it throughout the project navigation. Replace and remove controls would complete the workflow. For local projects, the asset could remain stored locally.
This would make Codex feel much more like an operating workspace for people managing several branded projects.
Here is a concrete mockup of how project-specific icons and colors could work in the Projects view:
Each project uses one simple glyph and one accent color. With 24 projects, the grid stays easy to scan without adding extra labels or UI chrome.
For automation, Codex could expose the available icons and colors and let agents or skills read and update them. A skill could then assign a consistent visual identity when it creates or registers a project.
Activity
github-actions commentedon May 31, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
idaibin commentedon Jul 15, 2026
It would be helpful to assign a color to each project and show that color before its pinned conversation titles.
For example:
Pinned
🔵 Task 1
🟢 Task 2
🟣 Task 3
Projects
🔵 Project A
🟢 Project B
🟣 Project C
This would make it easy to identify which project each pinned conversation belongs to at a glance.
haitibrand-co commentedon Jul 30, 2026
Adding a specific use case to this request: please let people upload the actual logo for a local Codex project.
I use Codex across several businesses and client workspaces. In the Projects view, identical folder markers slow recognition. A project logo would let me spot the right workspace immediately and help prevent prompts from landing in the wrong project.
A useful implementation could accept SVG or PNG files, fit the image inside the existing project marker, and display it throughout the project navigation. Replace and remove controls would complete the workflow. For local projects, the asset could remain stored locally.
This would make Codex feel much more like an operating workspace for people managing several branded projects.
pengusto commentedon Aug 18, 2026
Here is a concrete mockup of how project-specific icons and colors could work in the Projects view:
Each project uses one simple glyph and one accent color. With 24 projects, the grid stays easy to scan without adding extra labels or UI chrome.
For automation, Codex could expose the available icons and colors and let agents or skills read and update them. A skill could then assign a consistent visual identity when it creates or registers a project.
Related: #25385