Feature request: Custom status labels for Codex tasks and chats

What variant of Codex are you using?

codex

What feature would you like to see?

Feature request

Please add user-defined status labels for Codex tasks/chats, with customizable names and colors.

Problem

A completed Codex conversation does not necessarily mean that the related work has been implemented. For example, a chat may only contain:

• A feature plan
• Technical research
• A diagnosis
• An implementation proposal
• Work that has been completed and verified

Currently, Codex supports organizing chats through features such as pinning, renaming, searching, and archiving. However, there is no easy way to distinguish planned work from implemented work when a project contains many chats.

As a result, I need to reopen conversations and read their contents to determine the actual project progress.

Proposed solution

Allow users to create and assign custom status labels to tasks/chats.

Example statuses:

• Pending
• Planned / Not Implemented
• In Progress
• Implemented
• Blocked
• Needs Verification

Each status should have a user-selectable name and color.

The status should be visible as a colored badge or indicator next to the task title in the project sidebar and task list.

Suggested behavior

• Create, rename, reorder, recolor, and delete custom statuses
• Configure reusable statuses per project
• Assign or change a status from the task context menu or header
• Display the status color next to each task
• Filter, sort, or group tasks by status
• Preserve the status when a task is archived and restored
• Keep this status separate from Codex runtime states such as running, waiting, or completed
• Do not automatically change a manually assigned status unless the user explicitly enables automation

Example workflow

1. Ask Codex to produce an implementation plan.
2. Mark the task as “Planned / Not Implemented.”
3. When development starts, change it to “In Progress.”
4. After implementation and verification, change it to “Implemented.”
5. Scan the project task list and understand overall progress from the status colors.

Benefits

This would make Codex much more useful for managing long-running projects with many planning and implementation conversations. It would provide a lightweight progress-tracking layer without trying to replace a full issue tracker such as GitHub Issues, Linear, or Jira.

Additional information

No response

The issue does not name files, tests, or entry points. Start by locating the Codex task and chat organization code, then determine how project task lists, archived tasks, and context-menu or header actions are implemented. Done would require an agreed design and complete support for customizable statuses, assignment, persistence, and display.