You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A way to view full output of background terminals #16935
I’m using Codex CLI to run long-running ML jobs (e.g., training / rollout), and the current /ps command only shows a summarized preview (last few lines) of background terminals.
There is currently no clear way to view the full live output of a running background task.
What is the expected behavior?
There should be a way to:
Attach to a background terminal (similar to tmux attach)
Or expand /ps into a full log view
Or stream full stdout of a selected job
Why is this important?
For long-running workloads, logs are critical for:
debugging
monitoring progress
detecting failures early
The current summarized view is not sufficient for these use cases.
Suggested solutions
Add /attach <job_id> to open full terminal view
Add /logs <job_id> to stream full output
Or allow toggling between "preview" and "full" mode in /ps
Additional context
This feels like a limitation compared to tools like tmux/screen, where full session output is accessible.
Better observability for background tasks would significantly improve the developer experience when using Codex CLI.
Additional information
No response
Reacted by Frederic Fortier, Alexey Menshutin, Tommaso Thea Cioni, Xeonacid, Huang Yuheng, Ritchie Ng, Jacob Ford, Oscar Thörn, Joseph Barbier and Asuka Minato
changed the title [-]No way to view full output of background terminals (/ps only shows preview)[/-][+]A way to view full output of background terminals[/+]on Apr 6, 2026
Full output matters, but the operator also needs a stable boundary between human inspection and model context. An /attach or /logs path that gives the human the full stream without forcing that whole stream back through the model would be ideal. Otherwise background jobs are either opaque or they become token sinks. That same separation between operator-visible receipts and model-visible context has been really important in MartinLoop-style runtimes.
Activity
github-actions commentedon Apr 6, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
[-]No way to view full output of background terminals (/ps only shows preview)[/-][+]A way to view full output of background terminals[/+]Keesan12 commentedon May 18, 2026
Full output matters, but the operator also needs a stable boundary between human inspection and model context. An /attach or /logs path that gives the human the full stream without forcing that whole stream back through the model would be ideal. Otherwise background jobs are either opaque or they become token sinks. That same separation between operator-visible receipts and model-visible context has been really important in MartinLoop-style runtimes.