Skip to content

Browser plugin is uninstalled and reinstalled during app startup #34069

Closed as duplicate

Description

@MlDenis

Environment

  • ChatGPT Desktop 26.715.31925 (build 5551)
  • macOS 27.0 (26A5378n), arm64
  • Browser plugin already installed and current

What happens

I observed the same sequence on two consecutive launches.

Browser availability starts as false and changes to true 70–125 ms later. The first bundled-plugin reconciliation has already captured a plugin list without Browser. It continues after availability is true and uninstalls the installed Browser plugin because it is not in that captured list. A queued pass then adds Browser back and installs it as missing.

Representative launch, timestamps in UTC:

19:15:48.546 reconcile started queued=false reason=startup
19:15:48.554 browser availability=false reason=browser-pane-disabled
19:15:48.621 browser availability=true reason=available

19:15:52.519 runtime marketplace written
             plugins=[chrome, computer-use, latex, visualize]
19:15:54.430 uninstall browser
             reason=not_in_bundled_marketplace_plugin_names

19:15:57.128 reconcile started queued=true reason=startup
19:15:59.361 runtime marketplace written
             plugins=[browser, chrome, computer-use, latex, visualize]
19:15:59.994 install browser reason=missing

Both passes materialized their marketplace from the current app bundle, so this is not a stale-cache issue. The first pass appears to use a stale feature-availability snapshot.

After the queued pass completes, Browser is installed again and works. During startup there is an unnecessary window where the plugin is absent.

Expected

An in-flight reconciliation should be cancelled or superseded when feature availability changes. Starting the app with a current Browser plugin and Browser enabled should perform no uninstall/install cycle.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    skillsIssues related to skills
    on Jul 18, 2026
  2. github-actions commented on Jul 18, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  3. MlDenis commented on Jul 18, 2026

    @MlDenis
    Author

    Duplicate of #26429. The false → true Browser availability transition and the stale in-flight reconciliation are the same failure mode described there. Closing this one in favor of the existing report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbrowserbugSomething isn't workingskillsIssues related to skills

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions