openai / openai/codex

Feature request: Project-level progress dashboard (Windows Codex app)

Open
#43,477 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Summary

I’d like a project-level “Development Progress Dashboard” in the Codex app for Windows to track long-running (weeks/months) development beyond individual tasks.

Problem

Today I can see per-task progress, but it’s hard to understand overall project status:

  • what’s done vs not started
  • which phase we are in
  • what is blocked / awaiting approval

Requested dashboard (one screen)

  1. Overall progress
  • progress bar (e.g., 72%)
  • total features / completed / in progress / not started / blocked / awaiting approval counts
  1. Phase progress (customizable phases)
  • Requirements, Design, Implementation, Unit Test, Integration Test, etc.
  • allow adding/removing/renaming phases per project
  1. Feature list with status
  • Not started / Designing / Implementing / Implemented / Testing / Done
  • Blocked / Awaiting approval / Skipped pending approval
  • (optional) per-feature sub-progress for design/impl/test
  1. Auto-updates by Codex
  • infer from repo + task history + commits + test results
  • distinguish “AI-estimated” vs “user-confirmed” states
  1. Change history (“what changed since last time”)
  • e.g., feature X moved to Implemented; overall 63% -> 68%
  1. Issues & remaining work
  • unresolved problems, TODOs, failing tests, unknown specs, technical blockers
  • questions Codex needs user input on
  1. Approval-pending / skipped work queue
  • table: item | status | reason | impact
  • actions: approve / reject / keep pending / ask Codex for alternatives
  • optional bulk-approve after impact review
  • after approval, automatically re-queue and resume at an appropriate time

Scope / environment

  • Codex app for Windows (latest)
  • Long-horizon development on a single repo with multiple features/milestones

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

The issue names no files, tests, or entry points; begin by locating the Windows app architecture and the task, repository, commit, and test-history components it would need to use. Done would require an agreed scope and implementation covering the requested project, phase, feature-status, history, issue, and approval views.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
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.