Feature request: Project-level progress dashboard (Windows Codex app)
Open
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)
- Overall progress
- progress bar (e.g., 72%)
- total features / completed / in progress / not started / blocked / awaiting approval counts
- Phase progress (customizable phases)
- Requirements, Design, Implementation, Unit Test, Integration Test, etc.
- allow adding/removing/renaming phases per project
- 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
- Auto-updates by Codex
- infer from repo + task history + commits + test results
- distinguish “AI-estimated” vs “user-confirmed” states
- Change history (“what changed since last time”)
- e.g., feature X moved to Implemented; overall 63% -> 68%
- Issues & remaining work
- unresolved problems, TODOs, failing tests, unknown specs, technical blockers
- questions Codex needs user input on
- 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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