ChatGPT Desktop does not render request_user_input UI for Cloud Work conversations

What issue are you seeing?

ChatGPT Work renders the structured request_user_input / “Ask User” UI inconsistently across clients for a Cloud Work conversation.

Observed behavior:

This suggests that the Cloud Work runtime can emit the structured user-input request, but the Desktop client does not render or route that Cloud Work event correctly. Because local execution renders the UI in Desktop, the component itself appears to exist in the Desktop client.

What steps can reproduce the bug?

1. Open ChatGPT Work on the web and select Cloud execution.
2. Ask the agent to use the Ask User tool, or give it a task that causes a request_user_input call.
3. Confirm that the web client shows the structured question UI with selectable options.
4. Run an equivalent Cloud Work task from the ChatGPT Desktop app, or open/continue the Cloud Work conversation there.
5. Observe that Desktop does not show the structured Ask User UI.
6. As a control, run an equivalent task using Local Work in Desktop.
7. Observe that Desktop can display the structured Ask User UI for the local task.

What is the expected behavior?

When Cloud Work emits a request_user_input event, ChatGPT Desktop should render the same structured Ask User UI as ChatGPT Web.

At minimum, the behavior should be consistent across supported Cloud Work surfaces. If a particular structured-input type is not supported in Desktop, the client should show a clear fallback question instead of silently omitting the UI.

Additional information

• Product surface: ChatGPT Work / ChatGPT Desktop
• Exact Desktop build and OS version were not captured for the initial report.
• Reproduced on August 28, 2026.
• This appears distinct from:
  • #10952, which concerns persistent Desktop conversation-state desync after request_user_input is called in Default mode.
  • #29104, which concerns availability of request_user_input in Default mode.
• In this report, the key issue is client-dependent rendering/routing for Cloud Work: the Web client displays the structured UI while the Desktop client does not.

🤖 This report was prepared with AI assistance.

No source files, tests, Desktop build, or OS are named. Start by reproducing the Cloud Work request_user_input flow in Desktop and compare it with Web and Local Work, then trace the Desktop event-routing and rendering entry points. Done means the structured Ask User UI appears consistently, or an explicit fallback is shown when unsupported.