Codex Desktop composer not cleared after message is sent when many image attachments are included

Environment:

• App: Codex Desktop
• Version: 26.422.30944 (build 2080)
• OS: macOS 26.4.1 (25E253)
• Date/time observed: 2026-04-26 around 19:14 Asia/Jakarta

Issue:
After sending a message with many image attachments, the message appears successfully in the conversation thread, but the original prompt and uploaded image chips remain stuck in the composer/input box. The send button area still looks active/loading, making it unclear whether the message is still pending or already sent.

Expected behavior:
Once the message is accepted and appears in the thread, the composer should clear the text and attachments, or show a reliable send-failed state if it did not actually submit.

Actual behavior:
The message is visible in the thread, but the same text and attachments remain in the input composer. This risks duplicate sends and makes the desktop app feel laggy/stuck.

Reproduction:

1. Open Codex Desktop on macOS.
2. Open an existing long thread.
3. Attach many screenshots/images.
4. Type a long prompt.
5. Send the message.
6. Observe that the sent message appears in the thread, but the original prompt and attachment chips remain stuck in the composer.

Local diagnostics:

• Codex process did not crash.
• Renderer/app-server showed noticeable CPU activity.
• macOS logs around the event showed repeated pasteboard/drag events for file URLs.
• Relevant log line:

DragAndDrop: Reentrant message: kDragIPCCompleted, current message: kDragIPCLeaveApplication

Impact:
This makes it unclear whether a message has been sent and can cause accidental duplicate submissions, especially on large prompts with multiple screenshots.