openai / openai/codex

Feature request for Codex: built-in Backlog / Tasks for Later

Open
#45,723 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

App

What feature would you like to see?

Feature request for Codex: built-in Backlog / Tasks for Later

It would be very useful to have a dedicated Backlog section directly in the Codex interface.

The idea is simple: users should be able to create many future tasks without executing them immediately.

For example:

  • Add VK authentication
  • Improve image uploads
  • Add moderation tools
  • Add notifications
  • Refactor the API
  • Fix a specific bug

These tasks should stay saved in the project until the user explicitly chooses to run one of them.

Ideally, each task could have statuses such as:

Draft / Planned / In Progress / Done

Useful features would include:

  • Create and edit tasks directly in the Codex UI
  • Keep tasks saved without automatically executing them
  • Reorder tasks by priority
  • Add notes or additional instructions
  • Associate tasks with a specific project
  • Click a “Run” button to start any selected task
  • Move completed tasks to a Done section
  • Never automatically start the next backlog task unless explicitly requested

This would effectively provide a lightweight built-in project backlog / task manager inside Codex.

It would be especially useful for developers who continuously discover new ideas and improvements while working on a project, but do not want Codex to execute them immediately.

I think this could significantly improve long-term project workflows in Codex.

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue. Start by locating the Codex interface and project/task persistence entry points, then define the backlog scope and verify that tasks can be created, ordered, saved, and run only through explicit user action.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.