[macOS][Computer Use] Native Finder-to-app file drop is not delivered

What version of the Codex App are you using (From “About Codex” dialog)?

26.527.31326

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

On macOS, Computer Use does not deliver a native Finder file payload to a Drop target in another app.

Computer Use can operate Finder and the destination app independently, select the source file, and interact with controls in either app. However, a drag from a verified Finder file coordinate to a visible Drop target completes without the destination receiving a Drop event.

This blocks end-to-end Computer Use verification of macOS apps whose supported input flow is Finder Drag & Drop. The same drag succeeds immediately when performed manually, so the destination Drop target and file are valid.

What steps can reproduce the bug?

1. Create a synthetic local file.
2. Open its containing folder in Finder.
3. Open a signed, sandboxed native macOS app with a visible file-URL Drop target.
4. Allow both Finder and the destination app in Computer Use.
5. Arrange the two windows side by side.
6. Use Computer Use to select the file and verify its screen coordinates.
7. Invoke a drag from that Finder coordinate to the destination Drop target:

``ts
drag({
app: "Finder",
from_x: <verified file x>,
from_y: <verified file y>,
to_x: <visible drop target x>,
to_y: <visible drop target y>
})
``

1. Observe that no Drop event is delivered and the destination UI remains unchanged.
2. Perform the same Finder-to-app drag manually and observe that the file is accepted immediately.

I reproduced this in both Finder list view and icon view, using multiple verified source and destination coordinates.

As an additional check, targeting the destination app while starting from the Finder coordinate fails with windowNotFoundAtPosition.

What is the expected behavior?

When the source and destination apps are both allowed, Computer Use should preserve the native macOS drag session across app windows and deliver the file URL payload to the destination Drop target.

If cross-app native drag payloads are intentionally unsupported, the drag operation should return an explicit unsupported-capability result instead of appearing to complete successfully.

Additional information

• Computer Use plugin version: 1.0.1000633
• Same-app clicks and controls work normally.
• No destination app crash occurs.
• The synthetic source file remains unchanged.
• No screenshots, session share, real filenames, or real local paths are attached because they may expose private workspace data.
• This report is specifically about Computer Use operating a third-party Finder-to-app native drag, not dragging files into the Codex chat UI.

The current drag API accepts a single app argument. The observed behavior may indicate that the gesture is scoped to one app window, but that is only an inference from the public behavior. Please classify this as either an implementation bug or a currently unsupported capability.