What version of the Codex App are you using (From “About Codex” dialog)?
All
What subscription do you have?
Pro
What platform is your computer?
macOS
What issue are you seeing?
I want a centralized place in the Codex app to monitor commands run by the agent.
Right now, command output appears inline in the chat history. For long-running work, multiple commands, dev servers, test watchers, or parallel tasks, this is hard to follow because I have to scroll through the thread and find the relevant command block.
Requested UX:
- Add a sidebar or panel showing all commands run in the current thread.
- Clearly mark commands as running, completed, failed, or canceled.
- Allow clicking a command to see full stdout/stderr logs.
- Keep live logs updating for active commands.
- Support pinning important commands, like dev servers or test watchers.
- Show command metadata: cwd, start time, duration, exit code, approval/escalation status.
- Include filters: active only, failed only, current turn, all thread commands.
- Make it available from the task sidebar, terminal area, or a dedicated command monitor panel.
Why this matters:
Codex can run many tools during a thread, but visibility gets worse as the thread grows. A command monitor would make long-running sessions easier to supervise, reduce duplicated commands, and make failures easier to debug without chasing command blocks in chat history.
Suggested acceptance criteria:
- I can open one panel and see every command Codex has run in the thread.
- I can immediately identify which commands are still running.
- I can inspect logs for any command without scrolling through chat.
- I can pin or keep important long-running commands visible.
What steps can reproduce the bug?
Uploaded thread: 03de52a4-ff56-4a32-a594-fbfb271138ea
What is the expected behavior?
No response
Additional information
No response
What version of the Codex App are you using (From “About Codex” dialog)?
All
What subscription do you have?
Pro
What platform is your computer?
macOS
What issue are you seeing?
I want a centralized place in the Codex app to monitor commands run by the agent.
Right now, command output appears inline in the chat history. For long-running work, multiple commands, dev servers, test watchers, or parallel tasks, this is hard to follow because I have to scroll through the thread and find the relevant command block.
Requested UX:
Why this matters:
Codex can run many tools during a thread, but visibility gets worse as the thread grows. A command monitor would make long-running sessions easier to supervise, reduce duplicated commands, and make failures easier to debug without chasing command blocks in chat history.
Suggested acceptance criteria:
What steps can reproduce the bug?
Uploaded thread: 03de52a4-ff56-4a32-a594-fbfb271138ea
What is the expected behavior?
No response
Additional information
No response