[CLI][Remote] “Close it there” is impossible from mobile and does not identify the writer-lock owner

Codex versions

• Standalone CLI: 0.155.0
• Codex bundled with Desktop: 0.149.0-alpha.4
• ChatGPT/Codex Desktop package: 26.818.31338

Operating system

Linux x86_64, kernel 6.17.0-35-generic

What happened?

A Codex conversation was being accessed from the ChatGPT mobile app through Remote. Running codex resume <session-id> on the connected computer displayed:

This conversation is open in another app
Close it there and press R to continue here.

The mobile app has no action to close or release that conversation. Leaving the chat, terminating the mobile app, and even powering off the phone do not release the writer lock. The lock is apparently retained by the Desktop/App Server on the connected host, but the CLI does not identify that owner.

The user is therefore sent to the wrong device and asked to perform an action that does not exist in the mobile UI. The practical recovery is to terminate the Desktop app or exit the blocked TUI and run codex fork <session-id>.

Steps to reproduce

1. Enable Remote on a computer running the Desktop app.
2. Open or continue a Codex conversation from ChatGPT mobile through Remote.
3. On the host, run codex resume <session-id> for that conversation.
4. Observe the “open in another app” screen.
5. Close/force-stop the mobile app or power off the phone.
6. Press R in the CLI.

Actual result

The conversation remains blocked. The CLI neither identifies the Desktop/App Server as the writer-lock owner nor provides a way to release, hand off, or fork the conversation.

Expected result

At least one of the following:

• Identify the actual writer-lock owner and host, for example Codex Desktop on <host>.
• Provide an explicit handoff/release action in Remote/Desktop.
• Offer Fork conversation directly from the blocked TUI.
• Replace Close it there with instructions that are possible in the relevant client.

Related issue

Related UX request: #44764. This report is specifically about incorrect/unactionable lock-owner guidance in a Remote/mobile workflow.

Start by reproducing the blocked codex resume <session-id> flow using the listed Remote/mobile steps, then trace the TUI's writer-lock message and its interaction with the Desktop/App Server. Done means the CLI identifies the actual lock owner and host, or provides actionable release, handoff, or fork guidance for the relevant client.