What version of the Codex App are you using (From "About Codex" dialog)?
26.422.30944 (2080)
What subscription do you have?
Unknown
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
When I start a background persistent terminal in the Codex App and the terminal run finishes, the UI does not show the expected persistent terminal component above the message input box.
My expectation is based on how subagents are displayed: after creating a subagent, a small component/card appears above the input box so the user can see and access that background entity. The same kind of UI affordance seems expected for a background persistent terminal after it has been started or completed, but no component appears.
There is no visible error message.
What steps can reproduce the bug?
- Open the Codex App.
- Start a background persistent terminal from a conversation.
- Let the command running in that persistent terminal finish.
- Look above the message input box.
Actual result: no persistent terminal component/card is shown above the input box.
Expected reference behavior: creating a subagent shows a small component/card above the input box.
What is the expected behavior?
The Codex App should show a visible persistent terminal component/card above the message input box after a background persistent terminal is started and/or after its command finishes, similar to the component shown for subagents.
The component should let the user discover that the persistent terminal exists and access its output/state from the main conversation UI.
Additional information
This report was filed from a local Codex App session using GitHub CLI. The subscription value is marked as unknown because it was not available from the local app metadata used while filing the issue.
What version of the Codex App are you using (From "About Codex" dialog)?
26.422.30944 (2080)
What subscription do you have?
Unknown
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
When I start a background persistent terminal in the Codex App and the terminal run finishes, the UI does not show the expected persistent terminal component above the message input box.
My expectation is based on how subagents are displayed: after creating a subagent, a small component/card appears above the input box so the user can see and access that background entity. The same kind of UI affordance seems expected for a background persistent terminal after it has been started or completed, but no component appears.
There is no visible error message.
What steps can reproduce the bug?
Actual result: no persistent terminal component/card is shown above the input box.
Expected reference behavior: creating a subagent shows a small component/card above the input box.
What is the expected behavior?
The Codex App should show a visible persistent terminal component/card above the message input box after a background persistent terminal is started and/or after its command finishes, similar to the component shown for subagents.
The component should let the user discover that the persistent terminal exists and access its output/state from the main conversation UI.
Additional information
This report was filed from a local Codex App session using GitHub CLI. The subscription value is marked as unknown because it was not available from the local app metadata used while filing the issue.