@chrome / computer-use broken after app upgrade: chrome-native-hosts-v2.json not refreshed, local marketplace not synced

Open 💬 1 comment Opened Jun 12, 2026 by phenix3443

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

26.609.30741

What subscription do you have?

plus

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Root causes (two separate bugs):

  1. ~/.codex/local-marketplaces/openai-bundled/ is NOT synced on app upgrade.

The bundled marketplace stays on the old version (26.601), so plugin cache
installs the old extension-host binary. The new app-server (26.609) and the
old extension-host (26.601) have a protocol mismatch → connection fails.
Fix: sync app bundle plugins to local marketplace on upgrade (same as
sync-local-marketplaces.sh already does for openai-curated).

  1. presence.pid in ~/.codex/chrome-native-hosts-v2.json is never updated after

app-server restart. It keeps pointing to the dead pid from the previous
session. The app-server therefore cannot locate the extension-host →
@chrome silently aborts every session after a restart.
Fix: app-server should write its own pid to presence on startup (or on first
Chrome plugin use).

Steps to reproduce:

  1. Upgrade Codex app (any version bump)
  2. Send @chrome command
  3. Response aborts with no error after "loading Chrome tools"

Expected: app upgrade refreshes plugin cache and presence.pid automatically.

What steps can reproduce the bug?

Feedback ID: 019ebc70-d050-7ca3-beaa-f5eafa0922d8

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗