Codex Projects dashboard with cross-project summaries, next actions, and global project search

Open 💬 2 comments Opened May 19, 2026 by 190239134

What variant of Codex are you using?

codex app

What feature would you like to see?

I would love a Codex Projects dashboard / cross-project organizer.

The core idea is a home view that can summarize and organize work across all Codex projects and threads, not just one active project at a time. Right now, Codex is extremely useful inside a single repo/thread, but once you have several active projects, it becomes easy to lose track of what happened where. The user has to mentally manage all project state, recent work, next steps, uncommitted changes, running servers, and pending follow-ups.

A dashboard could show each project with:

  • latest active threads
  • last activity time
  • recent summary of what changed
  • current branch / git status
  • whether there are uncommitted changes
  • running servers or background tasks
  • pending approvals / follow-ups
  • suggested next action

The high-value AI feature would be a global Codex chat that can answer questions across projects, for example:

  • “What did I do this week across all projects?”
  • “Summarize each active project and what the next step is.”
  • “Which projects have uncommitted changes?”
  • “Which threads are waiting on me?”
  • “Find all TODOs mentioned in my recent Codex sessions.”
  • “Which project is closest to shipping?”
  • “Open the RoofLeadOps project and continue from the last task.”
  • “Give me a weekly report of what changed in each repo.”

This would make Codex feel much more like an operating system for agent work instead of isolated project sessions.

Additional information

As users start running multiple agents and multiple projects, the bottleneck becomes organization, not code generation.

Agents create output fast, but users need a way to keep track of:

  • what happened
  • what changed
  • what needs review
  • what should happen next
  • which project needs attention

For agent-heavy users, a cross-project dashboard could become a daily home base. It would also increase retention because Codex would become the place users return to manage their ongoing work, not just a tool they open for one coding task.

View original on GitHub ↗

2 Comments

190239134 · 3 months ago

Codex has projects and thread history, but it lacks a cross-project “home/ops” view that summarizes and organizes ongoing agent work across projects.

leonelngande · 2 months ago

Adding a focused variant of this request from a heavy Codex Desktop user workflow.

The missing piece is not only a project dashboard, but a persistent Open Loops model that is visible per thread and aggregated globally.

Current pain:

  • The right-side Plan panel is useful for the active turn, but it is not durable thread memory.
  • Long-running threads often involve PRs, deploys, review watches, automations, exported handoffs, and deferred follow-ups.
  • When returning to an older thread, the user often has to ask "where were we?" or "what is still left to do here?"
  • This gets worse when running many parallel workstreams across backend, web, Android, iOS, support monitoring, and production investigations.

Suggested shape:

  1. Per-thread Open Loops panel
  • current objective
  • next action
  • pending PRs/reviews/deploys
  • blockers or decisions needed
  • deferred follow-ups
  • latest verified state
  • linked artifacts such as PRs, exports, rollout notes, screenshots, or local files
  1. Global Open Loops inbox
  • grouped by thread/project
  • sortable by active, blocked, waiting on user, waiting on PR review, waiting on deploy, stale
  • quick link back to the source thread
  • last updated timestamp and next concrete action
  1. Automatic maintenance

Codex should update open loops when it:

  • opens or updates a PR
  • starts or finishes review monitoring
  • creates/updates an automation
  • creates a thread export or handoff
  • reports a blocker
  • says "left to do", "next step", "waiting on", or "safe to merge"
  • observes PR/deploy/test state that changes the next action

The useful distinction:

  • Plan = current execution steps.
  • Open Loops = durable thread/project memory for future resumption.

This would reduce repeated context-recovery turns and make Codex much more reliable for users with many simultaneous long-running agent workstreams.