Chrome plugin file upload setFiles fails with Not allowed and upload forms can hang
Summary
The Chrome plugin can connect to Chrome and navigate normally, but repeatedly hangs/timeouts on an authenticated invoice upload form when trying to inspect controls, upload files, or capture a visual screenshot.
This blocked completing a browser task that required uploading receipt images through @Chrome only.
What happened
Using the Chrome plugin in Codex Desktop:
browser.user.openTabs()worked.browser.tabs.list()/browser.tabs.get()worked.- Navigation to
https://www.zoetispetcare.com/account/rewardsworked. - Reading
body.innerText()worked on the rewards dashboard and the initial invoice instructions page. - Clicking through to the invoice submission flow worked.
- Once on the actual invoice form (
/account/rewards/invoice), repeated Chrome-plugin calls timed out until the Node runtime reset.
Calls that timed out included:
tab.playwright.locator('input[type="file"]').count()tab.playwright.locator('input').count()tab.playwright.locator('body').innerText(...)tab.playwright.waitForEvent("filechooser", ...)combined with clicking upload text/buttonstab.cua.get_visible_screenshot()tab.dom_cua.get_visible_dom()
The timeout pattern was consistent: the page stayed open in Chrome, but the plugin call hung until the tool reported a timeout and kernel/runtime reset.
Expected behavior
The Chrome plugin should either:
- allow normal Playwright/CUA interaction with the upload form, including file chooser upload, or
- fail quickly with an actionable error explaining that the page/frame/control cannot be automated.
It should not hang until the runtime resets.
Actual behavior
Chrome-plugin calls against the invoice form repeatedly timed out. This made it impossible to continue the task through @Chrome, despite the browser tab being navigated and logged in successfully.
Environment
- Codex Desktop on macOS
- Chrome plugin / Codex Chrome Extension
- Browser: Google Chrome
- Site: authenticated Zoetis Petcare Rewards invoice submission form
- Date observed: 2026-05-07
Notes
This may be related to file upload controls, authenticated pages, page scripts, or the plugin's DOM/CUA bridge on this specific form. The important product issue is that the plugin gets stuck instead of returning a bounded failure.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗