codex - 💡(How to fix) Fix Codex Desktop in-app Browser Use runtime reports virtual clipboard missing until bootstrapped from Chrome runtime

Environment

• OS: Windows
• Codex Desktop
• In-app browser / Browser Use
• Bundled browser plugin version observed: 26.519.31651
• Bundled browser-use plugin version observed: 0.1.0-alpha2

Problem

The in-app browser Browser Use runtime can enter an incomplete state where text input requiring the virtual clipboard fails with:

Browser Use virtual clipboard is not installed

This breaks non-ASCII input, for example Chinese text in web forms. ASCII-only input such as dates or short values can still work, which makes the failure look application-specific at first.

Evidence

The in-app browser related bundled plugin directories existed, but the expected runtime entrypoint was missing:

<codex-home>\plugins\cache\openai-bundled\browser\26.519.31651\scripts\browser-client.mjs
<codex-home>\plugins\cache\openai-bundled\browser-use\0.1.0-alpha2\scripts\browser-client.mjs

The complete runtime entrypoint did exist under the bundled Chrome plugin:

<codex-home>\plugins\cache\openai-bundled\chrome\26.519.31651\scripts\browser-client.mjs

Before bootstrapping from the complete runtime, calls such as Browser Use fill, type, cua.type, or tab.clipboard.writeText failed with the virtual clipboard error.

After manually importing and running setupBrowserRuntime from the complete bundled Chrome runtime, the same in-app browser tab could successfully run:

tab.clipboard.writeText("Chinese text test")
tab.clipboard.readText()
locator("textarea").fill("Chinese text test")

Expected behavior

The in-app browser should load a complete Browser Use runtime by default, and virtual clipboard support should be available without manually bootstrapping from the Chrome plugin runtime.

Actual behavior

The default in-app Browser Use path can initialize without working virtual clipboard support. Non-ASCII input then fails with Browser Use virtual clipboard is not installed.

Impact

Authenticated browser workflows that need non-ASCII form input become unreliable. This is especially confusing because ASCII-only fields still work, so the failure appears only when entering localized text.