codex - 💡(How to fix) Fix Add an Agent View for managing multiple Codex agents from the TUI

What variant of Codex are you using?

CLI

What feature would you like to see?

I would like Codex CLI/TUI to provide an Agent View for managing multiple active and historical agent sessions from one place.

When working with multiple agents in parallel, users currently need to keep track of several sessions manually. This becomes hard when agents are running in different worktrees, waiting for user input, or finishing at different times.

The proposed Agent View would let users:

• Open a unified agent/session list from the TUI, for example with /agents or an empty-prompt left-arrow shortcut.
• See each agent's status, such as running, needs input, idle, done, or error.
• See the last response preview and recent activity time for each agent.
• Jump directly into an agent session from the list.
• Include agent sessions discovered from the current app-server and persisted subagent history, not only sessions spawned during the current TUI lifetime.

This would make parallel Codex workflows much easier to operate, especially when a user is delegating multiple independent implementation or investigation tasks.

Additional information

I have a local prototype branch implementing an initial version of this for the Rust TUI.

Current prototype behavior:

• /agent opens an Agents view.
• /agents is supported as an alias.
• Pressing left arrow on an empty prompt reopens the Agent View.
• The view includes currently loaded threads plus persisted SubAgent sessions from thread/list.
• Rows show status, relative updated time, and the latest assistant/agent message preview.
• Enter selects the target agent thread.

Validation run locally:

• cargo test -p codex-tui agent_view -- --nocapture
• cargo test -p codex-tui agents_alias_opens_agent_command -- --nocapture
• just fix -p codex-tui
• git diff --check

One limitation of the current prototype is that cross-process real-time status still depends on what the current app-server knows. A complete version may need a global session/agent registry so the Agent View can show all running Codex agents across projects and processes with live status.