[Bug] Computer Use frequently remains active in the UI after operations finish

What issue are you seeing?

When using Computer Use in Codex, the interface frequently gets stuck in the Computer Use view. Even after the computer interaction has finished, Codex does not exit the Computer Use interface as expected.

The key symptom is the failure to leave the Computer Use state after use, rather than a failure to start Computer Use.

Frequency: This happens repeatedly during normal use; an exact reproduction rate has not been measured.

Original report (Chinese):

发现使用computer use的时候老是会卡在使用的界面，明明使用完了都没有退出computer use

What steps can reproduce the bug?

High-level workflow from the reported experience; a minimal deterministic reproduction has not yet been captured:

1. Start a Codex task that uses Computer Use.
2. Allow Codex to perform the computer interaction.
3. After the interaction has finished, observe the Computer Use interface.
4. The interface frequently remains in the Computer Use state instead of exiting it.

The exact triggering task, prompt, and target application have not been provided.

What is the expected behavior?

Once the Computer Use interaction is finished and no further computer interaction is needed, Codex should leave the active Computer Use state and return to the normal conversation/task interface. The UI should accurately reflect that Computer Use is no longer in progress.

Additional information

• Product/feature: Codex / Computer Use.
• Exact Codex client and version: not provided.
• Operating system and version: not provided.
• Model and subscription: not provided.
• Screenshots, logs, and session/feedback ID: not provided with this initial report.
• Workarounds and recovery behavior: not yet documented.

This report describes the observed UI behavior only. It has not been established whether the underlying Computer Use session remains active or whether only the displayed UI state fails to update. No root cause is claimed.

No file, test, client version, or deterministic reproduction is provided. First reproduce the Computer Use workflow and determine whether the underlying session remains active or only the displayed UI state fails to update; done means the interface reliably returns to the normal conversation/task view after the interaction finishes.