Chrome plugin: agent-created tabs cannot use Bitwarden autofill autonomously

Open 💬 0 comments Opened Jul 28, 2026 by cantonalex

What version of the Codex App are you using?

  • ChatGPT/Codex desktop app: 26.721.41059
  • Bundled Codex CLI: 0.146.0-alpha.3.1
  • Chrome plugin bundle: 26.721.41059
  • Google Chrome: 150.0.7871.187

What subscription do you have?

Not included in this report.

What platform is your computer?

macOS 26.5.2

What issue are you seeing?

Codex cannot complete a fully autonomous login flow using credentials saved in the Bitwarden Chrome extension.

When Codex creates a tab with the Chrome browser-control plugin and navigates to a login page, the saved username and password do not autofill. Interacting with the Bitwarden UI then blocks browser automation with this message:

Chrome is blocking automation because another extension UI is open on this page. Complete or dismiss that extension UI in Chrome, then ask me to continue.

The same login page works normally in a tab opened by the user: Bitwarden fills the credentials, Codex can claim that user-created tab, submit the login, and reach the authenticated dashboard.

This means the login succeeds only after the user opens or prepares the tab. The agent cannot perform the requested workflow by itself.

What steps can reproduce the bug?

  1. Install and sign in to Bitwarden in Chrome.
  2. Save credentials for a website login page.
  3. Connect the Codex Chrome plugin.
  4. Ask Codex to open the login page and sign in using the saved autofill credentials, with explicit permission to log in.
  5. Let Codex create a tab using chrome.tabs.new() and navigate to the login URL.
  6. Observe that the username and password fields remain blank.
  7. Focus the username field or try to open Bitwarden's inline/extension UI.
  8. Observe that browser automation is blocked while the extension UI is open.
  9. Manually open another normal Chrome tab and navigate to the same login URL.
  10. Observe that Bitwarden autofills the saved credentials.
  11. Let Codex claim that user-created tab with chrome.user.claimTab().
  12. Observe that Codex can submit the form and complete login successfully.

Reproduced on the American Express Australia login page, but the behavior appears to be at the Chrome plugin / password-manager extension boundary rather than site-specific.

What is the expected behavior?

With explicit user permission to log in, Codex should be able to complete the flow without requiring the user to create or prepare the tab.

One supported behavior would be sufficient:

  • agent-created Chrome tabs trigger the same password-manager autofill behavior as normal user-created tabs; or
  • Codex can safely invoke/select a saved Bitwarden login and resume automation; or
  • the Chrome plugin provides a supported handoff-and-resume mechanism that does not require the user to create the tab.

The expected behavior is not to bypass browser or extension security. It is to provide an explicit, permission-aware path for using the user's existing password-manager autofill.

Additional information

  • The user explicitly authorized the login test.
  • Codex did not need the plaintext credential; the successful workaround relied on Bitwarden filling a user-created tab.
  • Workaround: user manually opens the login page, allows Bitwarden to fill it, then Codex claims the tab and submits the login.
  • No credentials, account data, logs, or session transcript are included because the workflow involved a financial account.

View original on GitHub ↗