openai / openai/codex

macOS Desktop Settings cannot disable migrated Sites plugin: targets obsolete sites@openai-bundled

Open
#46,257 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug skills
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

26.911.61220

What subscription do you have?

Pro

What platform is your computer?

Darwin 27.2.0 arm64 arm

What issue are you seeing?

The plugin service resolves the effective Sites installation as: sites@openai-curated-remote

It is enabled and installed by default. However, Desktop generates bundled-plugin exclusion state containing:
{"disabled-bundled-plugin-ids":["sites@openai-bundled"]}

The Settings/update path then attempts to operate on the obsolete bundled identity: sites@openai-bundled

That plugin is no longer the effective Sites plugin, and the operation surfaces the generic:
Failed to update plugin error.

What steps can reproduce the bug?
  1. Open Desktop Settings → Plugins.
  2. Attempt to disable Sites.
  3. Observe: Failed to update plugin.
  4. Fully quit and relaunch Desktop.
  5. Attempt to disable Sites again.
What is the expected behavior?

The Settings toggle should operate on the effective Sites plugin:
sites@openai-curated-remote
and successfully update its enabled state.

Additional information

Cache-regeneration check
I backed up and removed the generated exclusion-cache state, then fully quit and relaunched Desktop.
Desktop immediately generated a new exclusion-cache entry containing the same legacy identity:
{"disabled-bundled-plugin-ids":["sites@openai-bundled"]}

So this does not appear to be stale user cache that can be repaired by deleting generated state: the current Desktop build recreates the legacy mapping itself.

Migration evidence
Current Codex source contains the test:
plugin_installed_hides_bundled_sites_when_remote_sites_is_effective
That test verifies that when migrated remote Sites is effective, the exposed plugin is:
sites@openai-curated-remote rather than the legacy bundled Sites entry.

This appears consistent with a Desktop Settings/reconciliation path retaining the pre-migration bundled plugin ID while the plugin-list path has already migrated to the remote canonical ID.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Desktop Settings → Plugins update path and locate the reconciliation code that generates disabled-bundled-plugin-ids. Compare its use of sites@openai-bundled with the effective sites@openai-curated-remote identity, then read the test plugin_installed_hides_bundled_sites_when_remote_sites_is_effective. Done means the Sites toggle updates the effective plugin and no longer recreates the obsolete mapping.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.