[Windows] Browser automation can open dialogs but cannot save form changes

Open 💬 0 comments Opened Aug 2, 2026 by ryosukesato0911-ship-it

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

26.727.6591.0

What subscription do you have?

Not specified

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

On an authenticated local Home Assistant UI, Codex Desktop can inspect the page, open and close dialogs, and fill form inputs. It cannot activate the final action that saves a setting.

The issue occurs through both browser surfaces:

  • In-app browser: after a fresh Codex restart, navigation links, dialog-opening buttons, DOM-based clicks, and coordinate clicks do not change page state.
  • Chrome extension: dialog opening/closing and text entry work, but the final Create button does not save a new helper.

The Create button is visible and enabled. Normal button click, coordinate click, and Enter on the focused button all leave the dialog open and create nothing.

What steps can reproduce the bug?

  1. Open an authenticated Home Assistant Helper page in Codex Desktop.
  2. Select Create helper.
  3. Select Text.
  4. Enter a new helper name.
  5. Confirm the Create button is visible and enabled.
  6. Try each documented interaction independently:
  • Button click through the browser automation API
  • Coordinate click on the visible Create button
  • Enter on the focused Create button
  1. Observe that the dialog remains open and the helper is not created.

For the in-app browser, repeat after fully restarting Codex and opening a fresh in-app browser connection.

What is the expected behavior?

The final Create action should close the dialog and persist the new helper, so the helper appears in the list. When a user explicitly approves a concrete configuration change, Codex should be able to complete the same save action that the page exposes.

Additional information

No private URL, credential, or Home Assistant setting is included here. The test helper was not created; the dialog was closed without saving.

A previously persisted denial for the local Home Assistant origin in Codex's browser session configuration was cleared before the fresh in-app-browser test. The denial list remained empty, but the in-app browser clicks still did not change page state. Chrome extension form submission remained unresponsive even though its dialog interactions worked.

View original on GitHub ↗